[go: up one dir, main page]
Scribd
Upload
203 views2 pages

Sample User Story

Tom James, a new field technician for ABC Corp, must download the ABC Team app and login with his registered email address in order to start his work. The app allows Tom to enter his username and password, with the option to hide or show the password. Upon entering valid login credentials, Tom is taken to the home screen of the app and can begin his tasks.

Uploaded by

Vaishali Martires
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
203 views2 pages

Sample User Story

Tom James, a new field technician for ABC Corp, must download the ABC Team app and login with his registered email address in order to start his work. The app allows Tom to enter his username and password, with the option to hide or show the password. Upon entering valid login credentials, Tom is taken to the home screen of the app and can begin his tasks.

Uploaded by

Vaishali Martires
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

User Story-Login for the app

Story summary –
Login-App - As a technician I want to login to the app with my registered email id so that I could start my work

Use case/User Scenario


Tom James is a new field technician who has just signed up with ABC Corp. ABC Corp has asked him to download
the “ABC Team” app from the app store. ABC Team app is a white-labeled / branded TrackHelp app.

ABC Corp has already registered Tom in the system.

Tom activates his Username and sets the password for his login.

Tom enters the Username and Password and clicks on the Sign In button.

By default, Tom’s password is hidden but he has the facility to show the password.

With the valid combination, he is able to log in to the app and is shown the Home screen of the app.

Acceptance Criteria
 Start button at the end of the Splash screens
 After the splash screens, on start Click, Tom is presented with a EULA (end-user licensing agreement),
with a check box that reads him to agree with and accept the EULA.

 Tom checks the check box and clicks the “Agree” button - upon which, Tom is presented with the new
/next page in the app.

User Experience Requirements

 Show “login” and “password” fields.


 Show Submit button.

 The password field should have “Hide” and “Show” functionality.

 Invalid instance details entered – display an error message

 Non-registered user tries to log in - display an error message

 Registered but not-activated user tries to log in - display an error message

 The user id is incorrect – display an error message

 Password doesn’t match – display an error message

 The account has been disabled – display an error message


 Invalid user for TrackHelp (user from another role in the system) tries to log in - display an error message

Data Input

Login Page:

1. Login -email id
2. Password

Data Output

Failed Scenarios

1. The splash screen does not load.


2. App crashes/does not load.

3. Incorrect login information entered.

4. Unregistered user tries to log in using some other/personal login/password.

5. The user is not able to log in due to server connectivity issues.

6. The user is not able to log in due to internet connectivity issues.

7. The user is not able to click/proceed ahead after the instance screen.

8. The user is not able to click on the Submit button.

9. The user is not redirected to the home screen after successful login.

10. The app does not proceed ahead/gets stuck after the Submit click.

11. The login process takes long time.

Error Messages & Error Handling

Any specific messages to be listed.

You might also like