| Age | Commit message (Collapse) | Author |
|---|
|
feature/expose_admin_in_api
|
|
|
|
So that whoever consumes the API can use this attribute to
determine if admin functionalities should be made available to
the current user.
|
|
with_config is not mean to test the current config. It will
set the config. So instead we need to look into APP_CONFIG.
|
|
There was a lot of special case handling going on in the users_controller
for this. Lot simpler this way.
|
|
Otherwise this will mess up other tests.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
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.
|
|
rails 4 mixes model, controller and integration tests. So lets
give this one a better name
|
|
but you may not hand it a nil
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
Rails 4.2 runs all tests mixed together. So unit tests and integration tests
may not have conflicting names.
|
|
AccountLivecycleTest -> CRUD accounts
SecurityTest -> security specific tests
AdminTest -> admin specific tests
|
|
we need to require 'capybara/rails' so that Capybara::DSL is available.
ActionController::RecordIdentifier was moved to ActionView
|
|
|
|
|
|
|
|
create/delete test & tmp users.
|
|
configured auth token.
|
|
token, "tmp" users are users that exist only in tmp db, "test" users are either tmp users or users named "test_user_x"
|
|
are configured in the static config, to be used for infrastructure monitoring.
|
|
get re-enabled.
|
|
anymore. closes #7690
|
|
Braintree_implementation
|
|
Admin - Ability to enable/disable user
|
|
Removing some superfluous code, mostly, and structuring tests better.
|
|
|
|
|
|
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.)
|
|
Introduce a invite_max_uses property to invite codes to allow admins to set a maximum number of uses for invite codes.
|
|
Through the config param 'invite_required', providers can decide whether users need to provide an invite code upon signup.
The default setting is false.
|
|
|
|
|
|
Handing freshly generated invite codes to Factory Girl to make the tests pass
|
|
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
|
|
|
|
|
|
Validation should only happen for new records
User invite code was nil for invalid invite codes
Adding missing tests
|
|
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.
|
|
|
|
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.
|
