summaryrefslogtreecommitdiff
path: root/test
AgeCommit message (Collapse)Author
2014-07-02minor: rename TapiceroTest to ActionsTestAzul
that's what it actually tests
2014-07-01pid issue remains to be solved - revert to sth workingAzul
We've seen two instances of tapicero running on the production servers. The reason is that we are using two different places for the pid file - one for root and one for a normal user. In this scenario tapicero started by root will not notice the tapicero run as a normal user and vice versa. One idea was to solve this by always using /var/run/pid. However this also requires write privileges to that place which essentially only root has. So let's keep the two different places and just make sure we ALWAYS run tapicero as the same user.
2014-02-04prevent 409s and 412 and reraise them in testsAzul
Including tests that ensure this
2014-02-04test user deletionAzul
2014-02-04include sleep in the create_user part of the testsAzul
the changes feed and tapicero take some time to process the new user. Let's prevent timing issues by sleeping a second.
2014-02-04separate test setup test from actual testAzul
2014-02-04fix testsAzul
2014-02-04set db name correctly in tests and test itAzul
2014-02-04unify naming scheme - tapicero_test prefixAzul
2014-02-04first interesting testsAzul
2014-02-04add dummy integration testAzul
2014-02-04try to get require rubygems to work on travisAzul
2014-02-04initial test for running tapicero on travis ciAzul
2013-09-10use our own JsonStream and a created callback in CouchChangesAzul
2013-09-10bringing over couch_changes from leap_ca including testsAzul