Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

DubSmash Test Cases: Password Change, PIN Check, Phone Validation, and Video Functionality, Thesis of Computer Science

Test case descriptions for various features of the DubSmash entertainment system, including changing the password, checking the PIN, validating phone numbers, and checking video functionality such as likes, comments, and search options.

Typology: Thesis

2022/2023

Uploaded on 10/30/2022

private-id
private-id 🇮🇳

5 documents

1 / 21

Toggle sidebar

Related documents


Partial preview of the text

Download DubSmash Test Cases: Password Change, PIN Check, Phone Validation, and Video Functionality and more Thesis Computer Science in PDF only on Docsity! Test Case #: 1.1 System: DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Change Password Subsystem: PIN Design Date: 28/11/2004 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. Post-conditions 1. The new PIN '5555' is saved in the database Test Case 1 Step Action Expected System Response Pass/ Fail Comment 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 Test Case #: 1.2 System: : DubSmash Entertainment Designed by: ABC Executed by: Short Description: Test the ATM Change PIN service Test Case Name: Check PIN Subsystem: PIN Design Date: 28/11/2004 Execution Date: Pre-conditions The user has a valid account with a unique password. The current PIN is 1234 The system displays the main menu Test Case 2 Step Action Expected System Response Pass/ Fail Comment 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) the new PIN Pass 3 Re-enter '5555' The system displays a message of successful operation The system asks the user if he wants to perform other operations Pass 4 Click 'YES' button The system displays the main menu Pass 5 Check post-condition 1 6 Repeat steps 1,2,3 using another PIN say '6666' and click 'NO' button The system is exited and displays a greeting message asking the user to place his ATM card in the machine Pass 7 Check post-condition 2 8 Repeat steps 1,2, using another PIN say '7777' The system displays a message asking the user to confirm (re-enter) the new PIN Pass 9 Enter a wrong confirmation (say ‘9876’) The system displays a message of unsuccessful operation and asks the user to confirm the correct PIN Pass 10 Re-enter ‘7777’ The system displays a message of successful operation The system asks the user if he wants to perform other operations Pass Test Case #: 1.4 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Checks how many times the person can enter wrong OTP during login. Subsystem: Phone Number Design Date: 28/11/2004 Execution Date: Pre-conditions The user enters a valid phone number. Post-conditions 1. The registered mobile number is not-valid. 2. System is at fault as it is crashed. Test Case 4 Step Action Expected System Response 1 User install the app. The system displays a message asking the user to enter the phone number. 2 Enter '6350045189’ The system displays a message asking the user to confirm (re-enter) the phone number. 3 Press YES. The system sends an OTP to the entered phone number. 4 Enters the received OTP. The system checks and detects wrong OTP. It displays a message “Try Again.” 5 Check post-condition 1 6 User again enters wrong OTP. System detects wrong OTP and System Crash. Test Case #: 1.5 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Checks how many times the person can enter wrong OTP during login. Subsystem: Phone Number Design Date: 28/11/2004 Execution Date: Pre-conditions The user enters a valid phone number. Post-conditions 3. The registered mobile number is not-valid. 4. System is at fault as it is crashed. Test Case 5 Step Action Expected System Response 1 User install the app. The system displays a message asking the user to enter the phone number. 2 Enter '6350045189’ The system displays a message asking the user to confirm (re-enter) the phone number. 3 Press YES. The system sends an OTP to the entered phone number. 4 Enters the received OTP. The system checks and detects wrong OTP. It displays a message “Try Again.” 5 Check post-condition 1 6 User again enters wrong OTP. The system checks and detects wrong OTP. It displays a message “Try Again.” 7. User again enters wrong OTP The system checks and detects wrong OTP. System sends a warning saying that if the user enters wrong OTP again the user will be blocked. Test Case #: 1.6 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Checks if the likes are added to the video or not Design Date: 28/11/2004 Pre-conditions User likes a video. Post-conditions 1. Likes are updated to the video. Test Case 6 Step Action Expected System Response Pass/ Fail Comment 1 User likes the video. The system shows a heart symbol and adds it to total likes and updates the total likes. Pass Test Case #: 1.9 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Checks if reported comments are deleted by the system or not. Design Date: 28/11/2004 Pre-conditions Comment is reported minimum 5 times. Post-conditions 1. Comment is deleted by the system. Test Case 9 Step Action Expected System Response Pass/ Fail Comment 1 User reports a comment on a video. The system detects that the comment is reported as abuse by more than 5 users. System deletes the comment Pass Test Case #: 1.10 System: DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Checks if search option is working fine or not Design Date: 28/11/2004 Pre-conditions No condition. Post-conditions 1. System displays searched videos. Test Case 10 Step Action Expected System Response Pass/ Fail Comment 1 User searches for a video. System searches for videos with similar keywords and filters the videos accordingly. System displays the videos. Pass Test Case #: 1.11 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Checks if the song added to the uploaded video is synced properly or not. Design Date: 28/11/2004 Pre-conditions User makes a video and add song to it. Post-conditions 1. Song is synced with the video. Test Case 11 Step Action Expected System Response Pass/ Fail Comment 1 User makes a video and add song to it. The system checks the timeline and syncs the video with the added song accordingly. Pass Test Case #: 1.14 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Full Screen view . Design Date: 28/11/2004 Pre-conditions No Condition. Post-conditions 1. System Crashed. Test Case 14 Step Action Expected System Response Pass/ Fail Comment 1 User clicks on full screen for a video. The system full size the screen. Fail Test Case #: 1.15 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Change Quality. Design Date: 28/11/2004 Pre-conditions No Condition. Post-conditions 1. System displaying buffering. Test Case 15 Step Action Expected System Response Pass/ Fail Comment 1 User faces problem with internet while watching videos. The system detects network problem and lower the quality accordingly. Fail Test Case #: 1.16 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Change Quality as per user. Design Date: 28/11/2004 Pre-conditions No Condition. Post-conditions 1. System displaying buffering. Test Case 16 Step Action Expected System Response Pass/ Fail Comment 1 User changes the quality. The system tries to change the quality as per demanded by user but detects network issue. System displays connect to internet. Fail Test Case #: 1.19 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name: Profile Updation. Design Date: 28/11/2004 Pre-conditions No Condition. Post-conditions 1. Profile is updated. Test Case 19 Step Action Expected System Response Pass/ Fail Comment 1 User updates his/her profile. System apply changes as per asked by user and updates it on the profile section. Pass Test Case #: 1.20 System: : DubSmash Entertainment Designed by: ABC Executed by: Test Case Name:Feedback. Design Date: 28/11/2004 Pre-conditions No Condition. Post-conditions 1. Feedback is sended. Test Case 20 Step Action Expected System Response Pass/ Fail Comment 1 User sends a feedback. System checks and sends a report accordingly to the developer and all the members. Pass
Docsity logo



Copyright © 2024 Ladybird Srl - Via Leonardo da Vinci 16, 10126, Torino, Italy - VAT 10816460017 - All rights reserved