Scribd
Upload
114 views6 pages

UMS Testcases

1. The test cases validate different functions of a user management system (UMS) including changing passwords, validating phone numbers, and checking the number of incorrect OTP entry attempts during login. 2. The test cases include expected steps and system responses to validate functions such as changing a password, validating a new phone number by confirming the number and entering the OTP sent, and allowing multiple incorrect OTP entry attempts before warning the user or blocking them. 3. The test cases covered both success and failure scenarios, with post-conditions to validate the expected system states after the tests.

Uploaded by

Bhumika Biyani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
114 views6 pages

UMS Testcases

1. The test cases validate different functions of a user management system (UMS) including changing passwords, validating phone numbers, and checking the number of incorrect OTP entry attempts during login. 2. The test cases include expected steps and system responses to validate functions such as changing a password, validating a new phone number by confirming the number and entering the OTP sent, and allowing multiple incorrect OTP entry attempts before warning the user or blocking them. 3. The test cases covered both success and failure scenarios, with post-conditions to validate the expected system states after the tests.

Uploaded by

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

Test Case 1

Test Case #: 1.1 Test Case Name: Change Password


System: UMS Subsystem: PIN
Designed by: ABC Design Date: 28/11/2004
Executed by: Execution Date:

Pre-conditions
The user has a valid account with a unique password to login.
The current PIN is 1234.
The system displays the main menu.

Step Action Expected System Response Pass/ Comment


Fail
1 Click the 'Change PIN' button The system displays a message asking the user to enter the new PIN
2 Enter '5555' The system displays a message asking the user to confirm (re-enter)
the new PIN
3 Re-enter '5555' The system displays a message of successful operation
The system asks the user if he wants to perform other operations
4 Click 'YES' button The system displays the main menu
5 Check post-condition 1

Post-conditions
1. The new PIN '5555' is saved in the database
Test Case 2

Test Case Name: Check PIN


Test Case #: 1.2
Subsystem: PIN
System: : UMS
Design Date: 28/11/2004
Designed by: ABC Executed by:
Short Description: Test the ATM Change PIN Execution Date:
service

Pre-conditions
The user has a valid account with a unique password.
The current PIN is 1234
The system displays the main menu

Step Action Expected System Response Pass/ Comment


Fail
1 Click the 'Change PIN' button The system displays a message asking the user to enter the new PIN Pass
2 Enter '5555' The system displays a message asking the user to confirm (re-enter) Pass
the new PIN
3 Re-enter '5555' The system displays a message of successful operation Pass
The system asks the user if he wants to perform other operations
4 Click 'YES' button The system displays the main menu Pass
5 Check post-condition 1
6 Repeat steps 1,2,3 using The system is exited and displays a greeting message asking the Pass
another PIN say '6666' and user to place his ATM card in the machine
click 'NO' button
7 Check post-condition 2
8 Repeat steps 1,2, using The system displays a message asking the user to confirm (re-enter) Pass
another PIN say '7777' the new PIN
9 Enter a wrong confirmation The system displays a message of unsuccessful operation and asks Pass
(say ‘9876’) the user to confirm the correct PIN

10 Re-enter ‘7777’ The system displays a message of successful operation Pass


The system asks the user if he wants to perform other operations
Click 'NO' button The system is exited and displays a greeting message Pass
Check post-condition 3

Post-conditions
1. The new PIN '5555' is saved in the database
2. The new PIN '6666' is saved in the database
3. The new PIN '7777' is saved in the database

Test happy path


Test also failure condition (step 9)
Test Case 3

Test Case #: 1.3 Test Case Name: Check if the


System: : UMS entered phone no. is valid or not

Designed by: ABC Subsystem: Phone Number

Executed by: Design Date: 28/11/2004


Execution Date:

Pre-conditions
The user enters a valid phone number.

Step Action Expected System Response Pass/ Comment


Fail
1 User install the app. The system displays a message asking the user to enter the phone Pass
number.
2 Enter '6350045189’ The system displays a message asking the user to confirm (re-enter) Pass
the phone number.
3 Press YES. The system sends an OTP to the entered phone number. Pass

4 Enters the received OTP. The system checks and finds it is valid . It displays Main Menu. Pass
5 Check post-condition 1

Post-conditions
1. The registered mobile number is valid.
Test Case 4

Test Case #: 1.4 Test Case Name: Checks how many


System: UMS times the person can enter wrong
OTP during login.
Designed by: ABC
Subsystem: Phone Number
Executed by:
Design Date: 28/11/2004
Execution Date:
Pre-conditions
The user enters a valid phone number.

Step Action Expected System Response Pass/ Comment


Fail
1 User install the app. The system displays a message asking the user to enter the phone Pass
number.
2 Enter '6350045189’ The system displays a message asking the user to confirm (re-enter) Pass
the phone number.
3 Press YES. The system sends an OTP to the entered phone number. Pass

4 Enters the received OTP. The system checks and detects wrong OTP. Pass
It displays a message “Try Again.”
5 Check post-condition 1
6 User again enters wrong OTP. System detects wrong OTP and System Crash. Fail

Post-conditions
1. The registered mobile number is not-valid.
2. System is at fault as it is crashed.
Test Case 5

Test Case #: 1.5 Test Case Name: Checks how many


System: UMS times the person can enter wrong
OTP during login.
Designed by: ABC
Subsystem: Phone Number
Executed by:
Design Date: 28/11/2004
Execution Date:
Pre-conditions
The user enters a valid phone number.

Step Action Expected System Response Pass/ Comment


Fail
1 User install the app. The system displays a message asking the user to enter the phone Pass
number.
2 Enter '6350045189’ The system displays a message asking the user to confirm (re-enter) Pass
the phone number.
3 Press YES. The system sends an OTP to the entered phone number. Pass

4 Enters the received OTP. The system checks and detects wrong OTP. Pass
It displays a message “Try Again.”
5 Check post-condition 1
6 User again enters wrong OTP. The system checks and detects wrong OTP. Pass
It displays a message “Try Again.”
7. User again enters wrong OTP The system checks and detects wrong OTP. Pass
System sends a warning saying that if the user enters wrong OTP again
the user will be blocked.

Post-conditions
3. The registered mobile number is not-valid.
4. System is at fault as it is crashed.

You might also like