OTP Test Cases Part 3

Posted on by vijay

ABOUT OTP

A one-time password (OTP) is an automatically generated numeric or alphanumeric string of characters that authenticates a user for a single transaction or login session.

An OTP is more secure than a static password, especially a user-created password, which can be weak and reused across multiple accounts.

OTPs might replace traditional authentication login information or may be used in addition to it to add another layer of security.

OTP-COMMON TEST CASES

TC ID FEATURE TEST CASES/STEPS EXP RESULT
TC_OTP_33 OTP Objective: To validate if the OTP is delivered to the mobile phone number/email when the phone nunber/email are inactivated

Pre Req:
1. The user is a registered user in the application
2. Inactivate the registered number/email
3. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on Generate OTP button

 OTP has to be generated; however, will not be received to the concerned mobile number/email
TC_OTP_34 OTP Objective: To validate if the OTP is properly delivered when the user is in roaming

Pre req:
1. The user has to have the roaming facility ‘on’ in the mobile device
2. The user is a registered user in the application
3. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on Generate OTP button

 OTP has to be delivered to the mobile phone even when the user is in roaming
TC_OTP_35 OTP Objective: To validate if the OTP is received when the user is Flight Mode

Pre req:
1. The user has to ON the Flight mode in the mobile device
2. The user is a registered user in the application
3. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on Generate OTP button

 OTP has not to be received when the registered mobile device is in Flight mode

The OTP has to be received only when the registered device is in General mode
TC_OTP_36 OTP Objective: To validate if the OTP is generated when the mobile phone is switched off

Pre req:
1. The user has to switch off the mobile device
2. The user is a registered user in the application
3. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on Generate OTP button

 1. The OTP sms has to be received when the mobile device is switched on
TC_OTP_37 OTP Objective: To validate if the OTP entered in the field is in encrypted mode (based on requirement)

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on Generate OTP button
4. Enter the received OTP in the OTP/Security Password field

 The OTP has to be in the encrypted mode when the user enters the same in the password/OTP field
TC_OTP_38 OTP Objective: To validate if the user is able to copy the encrypted OTP and use the same for the next transaction

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on Generate OTP button
4. Enter the received OTP in the OTP/Security Password field
5. Copy the OTP that is entered in the OTP/Security password field (encrypted)
6. Paste the OTP in any text document

 The OTP has not to be copied

(OR)

OTP has not to be allowed for the next transaction
TC_OTP_39 OTP Objective: To validate if the user is able to get OTP on call when click/tap on ‘OTP on Call’ button (Button name depends on the requirement)

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on ‘OTP on Call’ button

 The user has to get a voice call on the registered number and the OTP details has to be provided
TC_OTP_40 OTP Objective: To validate if the user is getting call for OTP in stipulated time frame (As per requirement, generally within 1 min)

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on ‘OTP on Call’ button

 The user has to get a voice call on the registered number within the stipulated time limit (based on the requirement)
TC_OTP_41 OTP Objective: To validate if the user is getting call every time they click/tap on OTP on Call button

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on ‘OTP on Call’ button multiple times

 The user has to get the number of calls the number times they Click/Tap on ‘OTP on Call’ button providing different OTPs
TC_OTP_42 OTP Objective: To validate if the application is accepting the latest OTP when the user click/taps on the ‘OTP on Call’ button multiple times

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on ‘OTP on Call’ button multiple times
4. Enter the latest received OTP
5. Tap on submit button

 1. Entered OTP has to be displayed with encryption

2. The transaction has to be successfull.
TC_OTP_43 OTP Objective: To validate if the application is accepting the old OTP when the user click/taps on the ‘OTP on Call’ button again after receiving the call for the OTP

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on ‘OTP on Call’ button
4. After receiving the call, click/tap on ‘OTP on Call’ button
5. Enter the old OTP

 The error message has to be displayed and transaction has not to be processed
TC_OTP_44 OTP Objective: To validate if the user is able to receive the OTP in sms if they click/tap on ‘OTP on Call’ button

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on ‘OTP on Call’ button

 1. The OTP details has to be received only via call

2. No sms with OTP has to be received on the device
TC_OTP_45 OTP Objective: To validate if the user is able to receive the call for OTP when user is on another call

Pre Req:
1. User is registered user in the application
2. User has switched on the feature of call waiting in the settings in the device
3. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login into the application
2. Click/Tap on the ‘OTP on call’ button
3. User received call from some other number

 The user has to be notified about the new incoming call (OTP call)
TC_OTP_46 OTP Objective: To validate the number of attempts the user is allowed to enter OTP received (based on the requirement)

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on Generate OTP button
4. Enter wrong OTP multiple times

 1. The user has to be allowed to enter wrong OTP for the limited number of trials

2. The user account has to be locked if the number of trials exceed the limit (based on the requirement)
TC_OTP_47 OTP Objective: To validate if the support details are displayed if the user makes large number of attempts for OTP against same transaction and account is locked

Pre req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login to the application
2. Enter the required details
3. Click/Tap on Generate OTP button
4. Enter wrong OTP multiple times

 1. The user has to be allowed to enter wrong OTP for the limited number of trials

2. The user account has to be locked if the number of trials exceed the limit (based on the requirement)

3. Support details has to be displayed for reactivating the account (based on requirement)
TC_OTP_48 OTP Objective: To validate if the OTP is displayed when the user enters the OTP and minimizes the App and then maximize it again

Pre Req:
1. The user is a registered user in the application
2.  WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login into the application
2. Enter the required details
3. Click/Tap on the ‘OTP on Call’ button
4. Enter OTP in the Password field
5. Minimize the application
6. Maximize the application
7. Observe the Password field

 The OTP (password) has to be available in the Password field
TC_OTP_49 OTP Objective: To validate if the OTP is displayed when user enters the OTP and closes the App and launches it again

Pre Req:
1. The user is a registered user in the application
2.  WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login into the application
2. Enter the required details
3. Click/Tap on the ‘OTP on Call’ button
4. Enter OTP in the Password field
5. Close the application
6. Reopen the application

 The user has to request the OTP again to complete transaction

[Varies on bussiness requirement]
TC_OTP_50 OTP Objective: To validate if the OTP is displayed when the user enters the OTP and locks the device

Pre Req:
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login into the application
2. Enter the required details
3. Tap on the ‘OTP on Call’ button
4. Enter OTP in the Password field
5. Lock the device
6. Unlock the device

 ER: The entered OTP has to be shown in the password field
TC_OTP_51 OTP Objective: To validate the latency between receipt of the OTP sms’ when requested multiple times

Pre Req
1. The user is a registered user in the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Login into the application
2. Enter the required details
3. Click/Tap on the submit button
4. Click/Tap on the Resend OTP button multiple times

 The sms with OTP has to be received in the message folder of the device with latency of 3-5 seconds depending on the requirement
TC_OTP_52 OTP Objective: To validate if the OTP can be requested while logging in the application

Pre Req:
1. The user is registered to use the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Enter the email id in the field
2. Click/Tap on the request OTP button

 The OTP has to be received to the registered device/email/token
TC_OTP_53 OTP Objective: To validate if the user is able to login the application with the requested OTP

Pre Req:
1. The user is registered to use the application
2. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Enter the email id in the field
2. Click/Tap on the request OTP button
3. Enter the OTP and click/tap on the submit button

 User has to be allowed to login application
TC_OTP_54 OTP Objective: To validate if the user is able to login using the requested OTP even after 15 mins of the request (based on the requirement)

Pre Req:
1. The user is registered to use the application
2. The application can be logged in only with the OTP (requirement)
3. WiFi/4G/3G/2G is turned ON on the test device

Test Steps:
1. Enter the email id in the field
2. Click/Tap on the request OTP button
3. Keep the application with out saving for 15 mins
4. Click somewhere in the application or just scroll up and down in the application
5. Enter the email id in the field
6. Enter the OTP that was requested 15 mins ago in the Password field

 The user has to be allowed to login into the application
TC_OTP_55 OTP Objective: To validate if the user is able to receive the OTP to the changed email when the user changes the registered email id

Pre Req:
1. The user is registered to use the application
2. The application can be logged in only with the OTP (requirement)
3. System has access to wifi/2G/3G/4G

Test Steps:
1. Login to the application
2. Change the registered email id to which OTP is required to be received
3. After 48 hours of the changing email id, enter the required details for the transaction
4. Click/Tap on “Generate OTP button”

 The user’s registered email id has to be changed

The OTP has to be received to the newly registered email id only after the 48 hours from the time of new email registration (the time may vary depending on the requirements)

New OTP has to be generated

Related Posts