| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2016-05-23 | move signup from users to account_controller | Azul | |
| There was a lot of special case handling going on in the users_controller for this. Lot simpler this way. | |||
| 2016-05-21 | tests: reset I18n.locale after locale_path_test | Azul | |
| Otherwise this will mess up other tests. | |||
| 2016-05-20 | include engine tests in default test | Azul | |
| 2016-05-20 | api: set defaults for version in routes | Azul | |
| This way we do not need to specify it all the times. In the functional tests defaults do not get added automatically. Introduced api_{get,put,post,delete} to add format and version default. One to two functional tests failing, everything else passes. | |||
| 2016-05-18 | api: allow version bumping - bump to 2 | Azul | |
| 2016-05-09 | test: make identity test locale independent | Azul | |
| It somehow managed to fail for a certain test order. Seems rather rare though - have not been able to reproduce it in 5 runs. Failed with --seed 60219. | |||
| 2016-05-09 | minor: cleanup debug message in test | Azul | |
| 2016-05-03 | use APP_CONFIG[config_file_paths] for provider.json | Azul | |
| This avoids overwriting the PROVIDER_JSON constant in the StaticConfigController and thus fixes test warnings. Also moved away from using instance variables in the ControllerExtension::JsonFile - instead querying the corresponding functions now - less sideeffects and easier stubbing. | |||
| 2016-05-03 | fix type mismatch TokenAuthTest | Azul | |
| rails 4 mixes model, controller and integration tests. So lets give this one a better name | |||
| 2016-05-02 | tests: Validator.new has optional options hash | Azul | |
| but you may not hand it a nil | |||
| 2016-05-02 | test: use assert_error_response in functional test | Azul | |
| This way the changed flash hash still is recognized. Also changed the generic 'no_such_thing' i18n key to more specific 'no_such_user'. The former is very hard to translate as the gender of thing may affect the translation of the 'no such' part. | |||
| 2016-05-02 | upgrade: use bootstrap3 variable names in leap.scss | Azul | |
| 2016-05-02 | upgrade: test cases now have #name | Azul | |
| 2016-05-02 | test: flash now has string keys | Azul | |
| 2016-05-02 | test: response is blank - not = ' ' | Azul | |
| 2016-05-02 | upgrade: default_wait_time -> default_max_wait_time | Azul | |
| 2016-05-02 | upgrade: unique test names | Azul | |
| Rails 4.2 runs all tests mixed together. So unit tests and integration tests may not have conflicting names. | |||
| 2016-05-02 | split up integration account test | Azul | |
| AccountLivecycleTest -> CRUD accounts SecurityTest -> security specific tests AdminTest -> admin specific tests | |||
| 2016-05-02 | fix browser_integration_test | Azul | |
| we need to require 'capybara/rails' so that Capybara::DSL is available. ActionController::RecordIdentifier was moved to ActionView | |||
| 2016-04-11 | allow monitor auth to create users even if invites are normally required. | elijah | |
| 2016-04-01 | api: added super simple motd, closes #7866 | elijah | |
| 2016-03-30 | api: return proper 404 for GET /1/identities/:id.json | elijah | |
| 2016-03-28 | api: added get(:show) to identities and users, allow monitors to ↵ | elijah | |
| create/delete test & tmp users. | |||
| 2016-03-28 | api: added allow ability to limit what IPs can access api using a static ↵ | elijah | |
| configured auth token. | |||
| 2016-03-28 | api tokens - clarify terms: "monitors" are admins that authenticated via api ↵ | elijah | |
| token, "tmp" users are users that exist only in tmp db, "test" users are either tmp users or users named "test_user_x" | |||
| 2016-03-28 | api tokens: allow for special api tokens that work like session tokens but ↵ | elijah | |
| are configured in the static config, to be used for infrastructure monitoring. | |||
| 2016-02-10 | allow user accounts to be re-enabled, and for associated identities to also ↵ | elijah | |
| get re-enabled. | |||
| 2016-01-31 | remove cert fingerprints for disabled users, so that they cannot send email ↵ | elijah | |
| anymore. closes #7690 | |||
| 2015-10-19 | Merge pull request #198 from claucece/develop | azul | |
| Braintree_implementation | |||
| 2015-10-19 | Merge pull request #196 from EvyW/develop | azul | |
| Admin - Ability to enable/disable user | |||
| 2015-10-06 | Integrated feedback on multi-invite codes | ankonym | |
| Removing some superfluous code, mostly, and structuring tests better. | |||
| 2015-10-05 | changed capybara time | claucece | |
| 2015-10-05 | add test to payments and subscriptions | claucece | |
| 2015-10-02 | Update rake task to allow generation of multi-use invites | ankonym | |
| The rake task now takes a second (optional) argument that sets the number of uses per invite code. If this is omitted, the default number of uses is 1. (This commit also contains some minor code cleanup that removes some stuff that I'd commented out but not removed.) | |||
| 2015-10-02 | Allow multi-use invite codes | ankonym | |
| Introduce a invite_max_uses property to invite codes to allow admins to set a maximum number of uses for invite codes. | |||
| 2015-09-28 | Make invite code configurable | ankonym | |
| Through the config param 'invite_required', providers can decide whether users need to provide an invite code upon signup. The default setting is false. | |||
| 2015-09-28 | Removed the view_by__id from invite code test | ankonym | |
| 2015-09-28 | Fixed the signup bug that wrongly consumes the invite code. | Aya Jaff | |
| 2015-09-28 | Fix the remaining failures/errors in our tests | ankonym | |
| Handing freshly generated invite codes to Factory Girl to make the tests pass | |||
| 2015-09-28 | Fix three unit tests by passing Factory Girl a valid invite code | ankonym | |
| The tests were failing because of a hardcoded "testcode" string so during test setup we generate a valid code and pass it to Factory Girl | |||
| 2015-09-28 | Fix several test failures by stubbing invite code validation | ankonym | |
| 2015-09-28 | Separate user and invite code validator tests | ankonym | |
| 2015-09-28 | Fixes for the invite code validator | ankonym | |
| Validation should only happen for new records User invite code was nil for invalid invite codes Adding missing tests | |||
| 2015-09-28 | Make sure codes can only be used once, fix validations | ankonym | |
| We introduced a count on invite codes to make sure that (at the moment) codes can only be used once. (The code will also allow multi-use codes in the future.) Also, some of our validations weren't validating against the correct data, which is now fixed. | |||
| 2015-09-28 | assign random invite code when creating new invite codes | ankonym | |
| 2015-09-28 | Remove change password browser test | ankonym | |
| Remove the change password test because the change password functionality is currently unused - however, it breaks with the new invite code field in the signup form. | |||
| 2015-09-28 | Fix test based on actual invite code validation | ankonym | |
| 2015-09-28 | Added an 'invite code' to all the tests for the sign-up form so we have a ↵ | Aya Jaff | |
| valid user for the tests again | |||
| 2015-09-28 | Adding invite code field to signup with validation for hardcoded invite code | ankonym | |
| 2015-09-21 | test users_controller_test | Evelyn | |
 |
index : leap_web.git | |
| [leap_web] | git repository hosting |
| summaryrefslogtreecommitdiff |