summaryrefslogtreecommitdiff
path: root/users/test/functional
AgeCommit message (Collapse)Author
2013-11-06use the account lifecycle from UsersController#destroyAzul
2013-10-30test helper to expect_logout.Azul
Currently it expects both the session and the token to be cleared. This might change. But we'll always have a definition of what it means to logout we can test this way.
2013-09-03Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properlyjessib
Bugfix/3623 teardown test data properly
2013-09-03Merge pull request #75 from azul/feature/token-expiryjessib
Token expiry
2013-09-03Cleanup sessions controller - webapp logs in through the api.Azul
So the #create and #update actions were not needed anymore. Also removed the tests
2013-09-03Account: Composition to handle User and its identitiesAzul
We have a lot of things that act upon a user record and one or more of it's identities at the same time: * Sing up: Create a user and it's initial identity * Rename: Change the username and create a new identity, turn old into an alias * Cancel Account: Remove user and all their identities. In order to keep the User and Identity behaviour isolated but still have a this logic represented in a sinle place the Account model deals with all these things. We could have overwritten the User#create, User#update and User#destroy methods instead. But then we would always create identities, even if we only need a user (for example in tests).
2013-09-03simplify users_controller_testAzul
2013-09-03expire token according to config setting auth:token_expires_afterAzul
2013-08-27separate different tests for showing non existant userAzul
This way the failed stubbing errors were more telling
2013-08-27token.user will get you the right userAzul
This way we can stub the token to return the user directly. Stubbing User.find_by_param is not a good idea as it will make all calls to User#find_by_param with a different id fail.
2013-08-27clear token on logout with testAzul
2013-08-27basic testing for token based auth in testsAzul
2013-08-27first steps towards enabling token based authAzul
2013-07-24separate signup and settings service objects for userAzul
2013-07-08Merge branch 'master' into feature/disable_accountjessib
Conflicts: users/app/controllers/users_controller.rb users/app/helpers/users_helper.rb users/app/views/users/edit.html.haml users/app/views/users/show.html.haml users/config/locales/en.yml
2013-07-04Add tests for enabling/deactivating.jessib
2013-07-04user tests -- user update has been moved entirely to api controller, so fix ↵elijah
tests to reflect this.
2013-07-01redirect to root_path after canceling accountAzul
login makes little sense. This change was applied already... just updated the test
2013-04-09adopting tests to new behaviorAzul
2013-04-09return token on successful login via apiAzul
2013-04-02send more meaningful error message on completely failed login attemptAzul
2013-04-02send salt on Session#create without srp ephemeral AAzul
2013-03-01Merge pull request #32 from azul/feature/api-version-1-fixesazul
Feature: API version 1 fixes
2013-02-26api for sessions fixedAzul
* now we return the user id on login * allow a destroy request for logging out * added test for api sessions controller
2013-02-25Admins cannot update a user. Eventually we will want to allow admins to ↵jessib
update some user fields.
2013-01-23functional test for webfingerAzul
2013-01-18minor: smalles fix ever - is_admin? has a questionmarkAzul
2013-01-17Should be able to create a user when not logged in.jessib
This isn't ready to merge, as there is an issue with logging in as an admin in the test.
2013-01-14Merge branch 'master' into feature/show_user. Added new tests.jessib
Conflicts: users/test/functional/users_controller_test.rb
2013-01-14got users controller test to pass - tickets controller test next.Azul
2013-01-10Add test for showing user.jessib
2012-12-18adopted functional tests to new controller designAzul
2012-12-18adjusted tests - we now reload the user so invalid records are clearedAzul
Actually that might not be the best idea. Issue at hand was that invalid email aliases were getting displayed when rendering the edit form again. We probably want to solve this different.
2012-12-17fixed inclusion of stub record helperAzul
2012-12-17fixed all user functional testsAzul
2012-12-07Merge branch 'master' into help_developjessib
Conflicts: app/views/layouts/application.html.haml help/app/controllers/tickets_controller.rb help/test/functional/tickets_controller_test.rb users/test/support/stub_record_helper.rb
2012-12-07fixed test to work with edit view that includes email and email forward.Azul
2012-12-03refactored tests with new find_record helperAzul
find_record User will return a stubbed user record and make sure User.find_by_id(user.id) returns the same so it can be used in controllers.
2012-12-03enable users to cancel their accountAzul
2012-12-03enable admin to edit usersAzul
2012-12-01Merge branch 'develop' into help_developAzul
2012-11-28admins can destroy usersAzul
I changed the permissions a little to be more consistent. Now: * admins can edit users * users can destroy themselves. There's no ui for either of them but theoretically they could. Not sure this is what we want though.
2012-11-26Merge branch 'develop' into help_developjessib
Conflicts: users/app/views/sessions/_nav.html.haml
2012-11-26simplified controller and adjusted testsAzul
Also added #assert_json_error to tests.
2012-11-23identify user by id so rerendering the form does not use new invalid loginAzul
2012-11-23refactored creation of record stubsAzul
2012-11-23test editing user settingsAzul
2012-11-22fixed testsAzul
2012-11-12Merge branch 'develop' into help_developjessib
Conflicts: help/test/functional/tickets_controller_test.rb users/test/functional/application_controller_test.rb users/test/support/auth_test_helper.rb
2012-11-12some notes to test that aren't working now.jessib