Age | Commit message (Collapse) | Author | |
---|---|---|---|
2013-09-17 | integration tests for session expiry | Azul | |
2013-09-04 | use /login instead of /sessions/new and test successful login | Azul | |
2013-09-03 | Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properly | jessib | |
Bugfix/3623 teardown test data properly | |||
2013-09-03 | cleanup records after running user integration tests | Azul | |
2013-09-03 | integration test for displaying internal server error during signup | Azul | |
2013-08-21 | use the same login validations on sessions and users | Azul | |
The session ones were outdated so valid usernames could not login if they contained a '.' Refactored so both models use the same module for this validation to ensure consistency. | |||
2013-08-08 | close srp vulnerability and report error in webapp | Azul | |
2013-08-07 | integration test exploiting srp vulnerability | Azul | |
2013-07-16 | ensure the page has been reloaded before testing current_path | Azul | |
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-15 | require test_helper from account test so it can be run in isolation | Azul | |
2013-07-14 | make sure capybara runs the whole rack app | Azul | |
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-14 | we do not expose M2 in srp.js anymore. | Azul | |
So there is no way to print it. This message used to be correct but there are also other things that can cause this to fail now. So let's just remove it. | |||
2013-07-14 | js integration test for signup, login, logout | Azul | |