leap_web.git - [leap

Age	Commit message (Collapse)	Author
2013-11-06	use the account lifecycle from UsersController#destroy	Azul

2013-10-30	test 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-03	Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properly	jessib
	Bugfix/3623 teardown test data properly
2013-09-03	Merge pull request #75 from azul/feature/token-expiry	jessib
	Token expiry
2013-09-03	Cleanup 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-03	Account: Composition to handle User and its identities	Azul
	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-03	simplify users_controller_test	Azul

2013-09-03	expire token according to config setting auth:token_expires_after	Azul

2013-08-27	separate different tests for showing non existant user	Azul
	This way the failed stubbing errors were more telling
2013-08-27	token.user will get you the right user	Azul
	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-27	clear token on logout with test	Azul

2013-08-27	basic testing for token based auth in tests	Azul

2013-08-27	first steps towards enabling token based auth	Azul

2013-07-24	separate signup and settings service objects for user	Azul

2013-07-08	Merge branch 'master' into feature/disable_account	jessib
	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-04	Add tests for enabling/deactivating.	jessib

2013-07-04	user tests -- user update has been moved entirely to api controller, so fix ↵	elijah
	tests to reflect this.
2013-07-01	redirect to root_path after canceling account	Azul
	login makes little sense. This change was applied already... just updated the test
2013-04-09	adopting tests to new behavior	Azul

2013-04-09	return token on successful login via api	Azul

2013-04-02	send more meaningful error message on completely failed login attempt	Azul

2013-04-02	send salt on Session#create without srp ephemeral A	Azul

2013-03-01	Merge pull request #32 from azul/feature/api-version-1-fixes	azul
	Feature: API version 1 fixes
2013-02-26	api for sessions fixed	Azul
	* now we return the user id on login * allow a destroy request for logging out * added test for api sessions controller
2013-02-25	Admins cannot update a user. Eventually we will want to allow admins to ↵	jessib
	update some user fields.
2013-01-23	functional test for webfinger	Azul

2013-01-18	minor: smalles fix ever - is_admin? has a questionmark	Azul

2013-01-17	Should 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-14	Merge branch 'master' into feature/show_user. Added new tests.	jessib
	Conflicts: users/test/functional/users_controller_test.rb
2013-01-14	got users controller test to pass - tickets controller test next.	Azul

2013-01-10	Add test for showing user.	jessib

2012-12-18	adopted functional tests to new controller design	Azul

2012-12-18	adjusted tests - we now reload the user so invalid records are cleared	Azul
	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-17	fixed inclusion of stub record helper	Azul

2012-12-17	fixed all user functional tests	Azul

2012-12-07	Merge branch 'master' into help_develop	jessib
	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-07	fixed test to work with edit view that includes email and email forward.	Azul

2012-12-03	refactored tests with new find_record helper	Azul
	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-03	enable users to cancel their account	Azul

2012-12-03	enable admin to edit users	Azul

2012-12-01	Merge branch 'develop' into help_develop	Azul

2012-11-28	admins can destroy users	Azul
	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-26	Merge branch 'develop' into help_develop	jessib
	Conflicts: users/app/views/sessions/_nav.html.haml
2012-11-26	simplified controller and adjusted tests	Azul
	Also added #assert_json_error to tests.
2012-11-23	identify user by id so rerendering the form does not use new invalid login	Azul

2012-11-23	refactored creation of record stubs	Azul

2012-11-23	test editing user settings	Azul

2012-11-22	fixed tests	Azul

2012-11-12	Merge branch 'develop' into help_develop	jessib
	Conflicts: help/test/functional/tickets_controller_test.rb users/test/functional/application_controller_test.rb users/test/support/auth_test_helper.rb
2012-11-12	some notes to test that aren't working now.	jessib