summaryrefslogtreecommitdiff
path: root/test
AgeCommit message (Collapse)Author
2014-04-17move support classes into their own packageAzul
now the webapp_login test looks nice and clean. soledad next.
2014-04-17nagios test: refactor webapp_login with classesAzul
2014-04-17refactor: move nagios specifs to nagios_testAzul
nagios_test.run takes a function and executes it. If it returns nothing or 0 and OK nagios message is printed. If it returns sth. else this will be printed a a warning If it raises an exception that will result in a CRITICAL report. This way we can keep the nagios things outside the test cases and just write simple functions that either return 0, a warnign or raise a meaningful exception
2014-04-17refactor reporting in webapp login nagios testAzul
2014-04-17refactor nagios tests, remove parseAzul
2014-04-11move include AssertResponses into test itselfAzul
it may not have been required before the RackTest support class.
2014-04-11move engines into engines directoryAzul
Also renamed help to support so it's harder to confuse it with documentation
2014-04-10move certs into toplevelAzul
cleaned up all the engine stuff that was never really used. Afterwards there is not that much left that makes it into the toplevel.
2014-04-08only load */test/factories from test/factoriesAzul
prevent recursive loadign of test/factories.rb ** can be empty.
2014-04-08moving users: app and test filesAzul
2014-04-08fix requiring core extensions - most tests passAzul
some message tests are failing for me right now.
2014-04-08moving all of core into toplevel, tests fail.Azul
2014-04-02Fix soledad sync nagios plugin returned check_name (#5430).db
2014-03-07Add script to check if soledad is working (#5239).db
2014-03-02including chiiphs commentsAzul
2014-03-02autopep8 nagios webapp login testAzul
2014-02-27nagios test for logging into webappAzul
2014-02-10refactor tests to ease the testing of token only authAzul
2014-02-07log failing integration tests with screenshotAzul
* store the last screenshot in tmp * store the html and the end of the server log in tmp Filenames are build from the test class name and the tests name.
2014-02-06integration test with en-EN languageAzul
Tests fail on machines that default to other available languages. Also move setting capybara driver to be javascript driver into the BrowserIntegrationTest.
2013-12-29Return 'provider.json' via a controller, to better be able to control the ↵elijah
response headers (in particular, 'X-Minimum-Client-Version'). It must now be placed in config/provider/provider.json
2013-12-22locale prefix support:elijah
* set locale based on request header * enforce locale path prefix when current locale is not the default * note: don't use root_path anymore, instead use home_path
2013-12-13minor: rename testAzul
2013-10-15detect os in browser and show proper download linkAzul
We add a class to the html element based on the detected os and use that to pick which download link should be visible. If we detect an os that is not supported we display a deactivated download link instead with all alternatives.
2013-09-17integration tests for session expiryAzul
2013-09-03integration test for displaying internal server error during signupAzul
2013-09-03Test the error handling of json and html responsesAzul
2013-07-24validations of email format and local domain moved overAzul
2013-07-16ensure the page has been reloaded before testing current_pathAzul
This test would fail sometimes on assert_equal '/', current_path I believe it was a timing issue. page.has_content? will wait for the content to show up. So afterwards the current_path should always be correct.
2013-07-14make sure capybara runs the whole rack appAzul
We use port 3003 for the integration test server. This test takes a few seconds (~8) now. Most of this is startup time of the server. A second run still takes 2 seconds like before.
2013-07-14js integration test for signup, login, logoutAzul
2013-07-01print couch version in test couch setupAzul
This way we can track down couch version related issues on travis.
2013-03-06simulate couch migration workflow on travisAzul
* first setup couch similar to what we'll have on the platform * then run migrations as admin * then drop admin privileges * then proceed with the normal test script
2013-01-11basic dummy data for usersAzul
2012-11-19use latest mocha version without monkey patching :)Azul
2012-11-04fixing tests, including support files from all enginesAzul
2012-10-24basic admin controller methods and helpers + testsAzul
2012-10-11fixed cert tests - adding test data and not testing the inline cert download ↵Azul
filename
2012-10-11lets not track the logs in version controllAzul
2012-10-08removed tmp cache files in dummy test dirAzul
2012-10-08use couchrest session store in core, updated dummy pathAzul
2012-10-05adding mocha for testsAzul
2012-09-27Adding in what used to be leap webapp demoAzul
we're merging repositories into one