leap_web.git/users/test, branch 0.2.3

Merge pull request #82 from azul/feature/sessions-expire

2013-09-19T17:41:58+00:00

Feature/sessions expire

user.account shortcut to Account.new(user)

2013-09-18T08:27:19+00:00

integration tests for session expiry

2013-09-17T11:04:11+00:00

use /login instead of /sessions/new and test successful login

2013-09-04T08:46:15+00:00

Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properly

2013-09-03T17:48:13+00:00

Bugfix/3623 teardown test data properly

Merge pull request #75 from azul/feature/token-expiry

2013-09-03T17:43:34+00:00

Token expiry

Merge pull request #76 from azul/feature/3600-visual-feedback-on-failed-signup

2013-09-03T17:38:39+00:00

Ensure json requests get json error response on failure

Cleanup sessions controller - webapp logs in through the api.

2013-09-03T08:49:00+00:00

So the #create and #update actions were not needed anymore. Also removed the tests

Account: Composition to handle User and its identities

2013-09-03T06:54:25+00:00

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).

cleanup records after running user integration tests

2013-09-03T06:54:25+00:00