Login of a returning user
Description:
The process of logging into an existing account of a registered user who wish to access Chomp’s functionalities.
Actors:
All registered users.
Trigger/
A registered user is returning to the site without a login cookie in their browser.
Action/
At the centre of the screen the both username or e-mail field and password field will display for the user. Once the fields are filled out, the user clicks the Login button. If any error occurs, the user is notified of the problem (in a semi specific manner that helps users without assisting intrusion attempts). If no error occurs the user is taken to their Chomp homepage. If an unregistered username or e-mail is entered, the registration process should begin for the user with a notice that the e-mail does not seem to be registered yet.
Acceptance Tests: (write test later)
Case 1-a: An unregistered e-mail should be tried, at which time the user should be alerted with an error message. The system should stay on the same page with previously filled out email intact, but password should be wiped clean.
Case 1-b: Non-email format is be entered with any password combination, at which time the user should be alerted with an error message same as Case 1-a. The system should stay on the same page with previously filled out email intact, but password should be wiped clean.
Case 2: A registered email and incorrect password should be entered, at which time an error message should appear (the message should be same as the invalid e-mail error message). The system should stay on same page with previously filled out email intact, but password should be wiped clean.
Case 3-a: A registered email and correct password should be entered, at which time the system should authenticate the user and keep it in a session. The system should redirect user to home page (page that is restricted to authenticated users only).
Case 3-b: User should be able to login to system with email address with different capitalization pattern.
Iteration: 1
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Essential
- Drafter:
- Eric Hedekar
- Direction:
- Approved
- Assignee:
- Jeyong Lee
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
- Implemented
- Milestone target:
- iter1
- Started by
- Eric Hedekar
- Completed by
- Jeyong Lee