| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2014-04-18 | Merge pull request #147 from azul/test/nagios-test-signup0.5.1-rc | azul | |
| Test/nagios test signup | |||
| 2014-04-17 | add a try/except for older versions of requests | Azul | |
| they have response.json as a dict instead of response.json() | |||
| 2014-04-17 | nagios test: also test registering new users | Azul | |
| 2014-04-17 | nagios test: use support classes in soledad sync | Azul | |
| 2014-04-17 | gitignore *.pyc | Azul | |
| 2014-04-17 | remove unneeded imports | Azul | |
| 2014-04-17 | move support classes into their own package | Azul | |
| now the webapp_login test looks nice and clean. soledad next. | |||
| 2014-04-17 | nagios test: refactor webapp_login with classes | Azul | |
| 2014-04-17 | refactor: move nagios specifs to nagios_test | Azul | |
| 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-17 | refactor reporting in webapp login nagios test | Azul | |
| 2014-04-17 | refactor nagios tests, remove parse | Azul | |
| 2014-04-17 | Merge pull request #146 from azul/refactor/engines | azul | |
| Refactor/engines | |||
| 2014-04-17 | doc: update list of engines | Azul | |
| 2014-04-11 | move include AssertResponses into test itself | Azul | |
| it may not have been required before the RackTest support class. | |||
| 2014-04-11 | minor: our engines do not have a db directory | Azul | |
| 2014-04-11 | move engines into engines directory | Azul | |
| Also renamed help to support so it's harder to confuse it with documentation | |||
| 2014-04-11 | moving broken billing integration tests out of the way | Azul | |
| They are currently using fake_braintree. I think this is not a good approach for integration tests. It's a fake - we should test against braintrees test api. However that requires getting an api key that we want to keep outside the repository. So these test can only run on travis if we manage to setup secret values in .travis.yml - which has been failing so far. So for now i moved the broken billing integration tests to billing/test/broken to move on. | |||
| 2014-04-11 | make sure billing tests do not interfere with others | Azul | |
| they are still broken though. | |||
| 2014-04-10 | bringing back srp js | Azul | |
| 2014-04-10 | move certs into toplevel | Azul | |
| 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-08 | only load */test/factories from test/factories | Azul | |
| prevent recursive loadign of test/factories.rb ** can be empty. | |||
| 2014-04-08 | move users: config and lib | Azul | |
| 2014-04-08 | moving users: app and test files | Azul | |
| 2014-04-08 | moving users: dependencies | Azul | |
| 2014-04-08 | update documentation: included core in toplevel | Azul | |
| now we only include some engines - we don't build the whole webapp based on them. Reflecting this in the documentation. | |||
| 2014-04-08 | move all dependencies into Gemfile | Azul | |
| We used to keep them separated so one could require some engines without using the full webapp. We've never really supported this though and probably never will. | |||
| 2014-04-08 | fix requiring core extensions - most tests pass | Azul | |
| some message tests are failing for me right now. | |||
| 2014-04-08 | moving all of core into toplevel, tests fail. | Azul | |
| 2014-04-04 | Merge branch 'bugfix/5382-rescue-token-destruction' into develop | elijah | |
| 2014-04-04 | redirect home when logged in visits /signup (#5446) | Azul | |
| 2014-04-04 | 5382 - prevent crash when destroying tokens | Azul | |
| An expired token was removed (probably by automatic cleanup) while processing it. So the webapp crashed due to a couch 404. We're preventing that by rescueing from a 404 on Token.delete by default. | |||
| 2014-04-02 | Merge pull request #143 from ↵ | varac | |
| andrejb/bug/5430_fix-soledad_sync-returned-check_name Fix soledad sync nagios plugin returned check_name (#5430). | |||
| 2014-04-02 | Fix soledad sync nagios plugin returned check_name (#5430). | db | |
| 2014-03-12 | Merge pull request #141 from andrejb/feature/5129_check-if-soledad-is-working | azul | |
| Add script to check if soledad is working (#5239). | |||
| 2014-03-07 | Add script to check if soledad is working (#5239). | db | |
| 2014-03-02 | including chiiphs comments | Azul | |
| 2014-03-02 | autopep8 nagios webapp login test | Azul | |
| 2014-02-27 | nagios test for logging into webapp | Azul | |
| 2014-02-10 | Merge pull request #139 from azul/refactor/tweaks-to-messages | jessib | |
| Refactor/tweaks to messages | |||
| 2014-02-10 | fix unread_by? to check user_ids_to_show, remove TODO | Azul | |
| uniq! is probably not any faster than just checking include? | |||
| 2014-02-10 | Merge pull request #138 from azul/feature/token-only-api-auth | jessib | |
| Feature/token only api auth | |||
| 2014-02-10 | ensure we are working on a string as the content type | Azul | |
| 2014-02-10 | require_token now checks for token and login | Azul | |
| 2014-02-10 | require token in messages controller | Azul | |
| 2014-02-10 | require token when logging out via API | Azul | |
| 2014-02-10 | require token when updating user via API | Azul | |
| 2014-02-10 | split up and expand account integration test | Azul | |
| 2014-02-10 | refactor tests to ease the testing of token only auth | Azul | |
| 2014-02-10 | minor: more robust destruction of records in tests | Azul | |
| 2014-02-10 | rename authorize to require_login | Azul | |
| authorize_admin -> require_admin also add require_token which will ensure token has been used for auth. | |||
 |
index : leap_web.git | |
| [leap_web] | git repository hosting |
| summaryrefslogtreecommitdiff |