Test Scenarios for TV
1.Verify the dimensions of the TV - length, breadth and height are as per the specifications2.Check the TV technology type - LED, LCD etc.
3.Verify that the screen resolution of the TV is as per the specifications
4.Check the material used for outer body of TV
5.Check the material used for screen of TV
6.Verify that on supplying specified power supply, TV gets switched on after pressing 'Power' button
7.Verify that all the buttons on TV perform there functioning correctly
8.Verify that TV screen clearly displays videos
9.Verify that audio of TV is audible without any noise
10.Verify that buttons in TV have clearly visible labels indicating there functionality
11.Verify that buttons in TV function correctly when pressed
12.Verify that remote's signal receiver receives signal within a specified range
-----------------------------------------------------------------------------------------------------------------------
Test cases of TV Remote Control
1.Verify that all the buttons are present- 0 to 9, volume, channel up-down and other audio-video functionality etc. buttons2.Verify the functionality of power ON-OFF button
3.Verify that the Remote Control should work for a particular TV set model numbers only
4.Verify that user can navigate to different single digit and multi digit channels
5.Verify that user can increase or decrease the volume
6.Verify that user can navigate up and down the channel using channel up and down buttons
7.Verify that functioning of audio-video and other auxiliary buttons
8.Verify the maximum distance from the Television set up to which the remote works smoothly
9.Verify the button press event that triggers the functionality i.e. an event gets triggered on button down press, button release etc.
10.Verify the arc/different directions the remote control works correctly
11.Verify the battery requirement of the remote control
12.Verify the material of the remote's body and its button
13.Verify the weight of the remote control
14.Verify the dimensions of remote control
15.Verify the spacing between two buttons, the spacing between the two buttons should be optimum distance apart so that user can press a button comfortably
16.Verify that there should be contrast between button's color and remote's outer body color
17.Verify the remote's functioning on pressing more than one button simultaneously
18.Verify that the font - style and size of the numbers and other information should be readable
19.Verify that on battery discharge, the remote should work normally on inserting new batteries
20.Verify the pressure required to press the button
21.Verify the strength of the remote's outer body, if it works normally on dropping from a certain height
22.Verify that any operation performed on the remote control while the TV is switched off should not make any difference to TV's functioning when switched on
23.Verify if the remote control is water proof or not, if its water proof, check if it works normally after immersing it in water
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios of Stapler
1.Verify that the stapler staples the paper firmly.2.Verify that the stapler works correctly with maximum number of paper sheets or maximum width of papers to be stapled.
3.Verify that stapler works correctly with materials other than paper that are commonly stapled things like cartridge sheet.
4.Verify the pressure required to staple is not too high.
5.Verify that the maximum number of pins that can be placed in stapler at a time is as per the specification.
6.Verify the dimension of the stapler.
7.Verify the outer material of stapler.
8.Verify the color of the stapler's outer body is as per the specifications.
9.Verify the width of the pins used in stapler.
10.Verify that the component to unstaple is present in the stapler (usually at the end).
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios for Table
1.Verify that the dimension of table is as per the specifications2.Verify that the weight of the table is as per the specifications
3.Check the height of the table's seat from floor
4.Verify that the table is stable enough to take specified load
5.Check the material used in making the table wood, plastic etc.
6.Check if the table's leg are level to the floor
7.Check the usability of the table as an office table, normal household table
8.Verify the paint's type and color
9.Verify if the table's material is brittle or not
10.Check if cushion is provided with table or not
11.Check the condition when washed with water or effect of water on table
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios of Triangle
1.Verify that the figure is closed (polygon).2.Verify that the figure is two-dimensional and formed with straight lines only.
3.Verify that the figure has exactly three sides.
4.Verify that the figure has exactly three vertices.
5.Verify that the sum of the angles of the figure is 180 degrees.
6.Verify that no two sides are perpendicular to each other
7.Verify that the sum of the length of two sides of the triangle should be greater than length of the third side
8.Verify that no two angles of triangle have 90 degree and above value.
9.Verify the type of triangle is as per the specification, based on its sides - scalene, isosceles or equilateral.
10.Verify the type of triangle is as per the specification, based on its angles - acute angle, obtuse angle or right angled triangle.
-----------------------------------------------------------------------------------------------------------------------
Test cases of Wrist Watch
1.Verify the type of watch - analog or digital2.Verify the RPM of second, minute and hour hand of the watch, in case of analog watch
3.Verify that digital display for hours, minutes and seconds is correctly displayed
4.Verify the material of the watch and its strap
5.Check if the shape of the dial is as per specification
6.Verify the dimension of the watch is as per the specification
7.Verify the weight of the watch
8.Check if the watch is water proof or not
9.Verify that the numbers in the dial are visible or not
10.Verify that the numbers in the dial are placed at equal distance
11.Check if the watch is having date, day display or not
12.Verify that clock's time can be corrected using the key in case of analog clock and buttons in case of digital clock
13.Check if the second hand of the watch makes ticking sound or not
14.Verify if the brand of the watch and check if its visible in the dial
15.Check if the clock is having stopwatch, timers and alarm functionality or not
16.In case of digital watch, verify the format of the watch 12 hour or 24 hour
17.Verify if the watch comes with any guarantee or warranty
18.Verify if the dial has glass covering or plastic, check if the material is breakable or not
19.Verify if the dial's glass/plastic is resistant to minor scratches or not
20.Check the battery requirement of the watch
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios of Water Bottle
1.Verify that the dimension of the bottle are as per the specifications2.Verify that the color of the bottle is as per the specifications
3.Verify the material used in bottle
4.Verify weight of the bottle is as per the specifications
5.Verify the type of the bottle - with lid or without lid
6.Check if the bottle is with sipper or without sipper
7.Measure the volume of water that can be stored in bottle and check if the volume is as specified
8.Verify that bottle doesn't leak with liquid stored
9.Verify that the lid of the bottle is firmly tightened with bottle
10.Check bottle's condition with liquid of different temperature
11.Check bottle's condition with different liquids - water, tea etc.
12.Check the insulation of bottle - time for liquid to achieves room temperature
13.Check the brittleness of the bottle's material
14.Check bottle's condition on pouring liquid at very high temperature
15.Check bottle's condition on pouring liquid at very low temperature
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios of WhatsApp
1.Verify that on downloading WhatsApp application, user can register using a new mobile number.2.Verify that for a new mobile number user will get a verification code on his mobile and filling the same verifies the new user account.
3.Check the maximum number of incorrect attempts allowed while filling the verification code.
4.Verify that registering an existing mobile number for new user account registration is not allowed.
5.Verify that on successful registration all the contacts in user's contact directory get imported to WhatsApp contact list.
6.Verify that user can set DP and status on WhatsApp.
7.Verify that user can update existing DP and WhatsApp status.
8.Verify that user can send message to any individual selected from his contact list.
9.Verify that 'Chats' window contains all the chat list with DP and name and last message preview of the other person with whom chat was initiated.
10.Verify that clicking a chat in the chat list opens a new window containing all the chats received and sent with the other person.
11.Verify that user can check the message delivered and read time for a message in the 'Message Info' section.
12.Verify that user can share or receive a contact with the other person.
13.Verify that user can create a group adding multiple person from his contact list.
14.Verify that user can send and receive message in group chats.
15.Verify that user can send and receive images, audio, video, emoticons in chat to individuals.
16.Verify that user can send and receive images, audio, video, emoticons in group chats.
17.Verify that user can send and receive chats in secondary languages available.
18.Verify that user can delete text, images, audio, video messages within a chat.
19.Verify that user can clear complete chat history in an individual or group chat.
20.Verify that user can archive chats in an individual or group chat.
21.Verify that user can block a user to prevent any message from getting received from the blocked contact.
22.Verify that user make WhatsApp calls to the person in his contact list.
23.Verify that user can receive WhatsApp calls from person in his contact list.
24.Verify that user can mark chats as favorite and access all chats marked as favorite from the 'Favorites' section.
Chat settings test scenario
1.Verify that user can set a chat wallpaper.
2.Verify that user set privacy settings like turning on/off last seen, online status, read receipts etc.
3.Verify that user can update notification settings like - notification sound, on/off, show preview for both group and individual chats.
4.Verify that user can take the complete chat backup of his chats.
5.Verify that user update his phone number that is used by WhatsApp application.
6.Verify that user can disable/delete his WhatsApp account.
7.Verify that user can check data usage by images, audio, video and documents in WhatsApp chats.
-----------------------------------------------------------------------------------------------------------------------
Test cases of White Board
1.Verify that the dimension of the white board are as per the specifications2.Verify the exact color of the board - white color's variant
3.Verify the smoothness of the white board
4.Verify the material used to develop surface of the white board
5.Verify the material used in the body of the white board, its hooks and other parts
6.Verify if the board is suitable for writing with normal/specified marker types
7.Verify if there is sufficient friction in the board to allow writing in its surface
8.Verify if text written in the board using normal markers gets erased using duster
9.Check if there is holder for markers and duster in the white board
10.Verify that board works normally in all climatic conditions- humidity, temperatures etc.
11.Verify that the board doesn't reflect too much light that makes it unreadable
12.Verify the amount of pressure required to write in the board using normal markers
13.Verify that markers of all colors but white should be visible on the board
14.Verify that text written in the board should not fade away quickly(or before a specified time)
15.Verify that the board has hooks to hang them over the wall
16.Verify if text written using permanent markers, paints etc. can be erased on the board using chemicals
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios for Video Upload Functionality
1.Verify that user can upload single video or allowed format and size successfully.2.Verify that while uploading user should select the video license and type of video along with its attributes like- name, artist name, company etc.
3.Verify the maximum size of video that is permitted to upload and check that any attempt to upload video of size greater than the allowed value results in an error message.
4.Verify if there is any minimum size of video that is permitted to upload and any attempt to upload file size less than specified results in error message.
5.Verify all the video formats that are allowed to upload - .mp4, .3gp, .avi etc. and check that uploading file formats other that allowed results in error message.
6.Verify that uploading blank file should result in error message.
7.Verify that user can upload multiple videos or allowed format and see successfully.
8.Verify that uploaders get notification of comments posted on the videos uploaded by them.
9.Verify that user can view likes, dislikes and comments for their videos.
10.Verify that user can reply to the comments posted in their videos.
Test scenarios for Video Viewing Functionality
1.Verify that video page can be opened by direct link to a video.
2.Verify that on clicking the video play icon over the video, the video should play.
3.Verify all the video player controls- play, pause, volume, mute etc.
4.Verify that user can select the allowed video quality for playing the video.
5.Verify that once the video is complete, user can replay the video using 'replay' icon.
6.Verify that video should be searchable by name, displaying the most relevant video on the top in search results.
7.Verify that other attributes of video like artist name, description should also be searchable.
8.Verify that user should get auto suggestions while searching for videos in the YouTube search bar.
9.Verify that search results should display information like video name, thumbnail, video length, view counts etc.
10.Verify that clicking the video thumbnails in the search results should lead to video page.
11.Verify that video filtering and sorting option while searching for video like - sort be view count, like, upload date etc.
12.Verify that user can view 'view count', 'comments', 'like' and 'dislikes' for a video.
13.Verify that with each view the 'view count' increases by one.
14.Verify that user can like or dislike a video and the corresponding count should increase by one.
15.Verify that user can comment in the comments section.
16.Verify that user should be presented with related videos in the sidebar section.
17.Verify that the related videos are related to the current video or is based on the past viewing history of user.
18.Verify that clicking related video thumbnail should open the video.
19.Verify that for age restricted video, user is asked to login to YouTube account.
20.Verify that logged-in user should see their history as well as recommended videos in the home page.
21.Verify that every video viewed goes to history for logged in user...
22.Verify that user can view or delete history items.
-----------------------------------------------------------------------------------------------------------------------
Database Testing Test Cases
1.Check if correct data is getting saved in database upon successful page submit2.Check values for columns which are not accepting null values
3.Check for data integrity. Data should be stored in single or multiple tables based on design
4.Index names should be given as per the standards e.g. IND_
5.Tables should have primary key column
6.Table columns should have description information available (except for audit columns like created date, created by etc.)
7.For every database add/update operation log should be added
8.Required table indexes should be created
9.Check if data is committed to database only when the operation is successfully completed
10.Data should be rolled back in case of failed transactions
11.Database name should be given as per the application type i.e. test, UAT, sandbox, live (though this is not a standard it is helpful for database maintenance)
12.Database logical names should be given according to database name (again this is not standard but helpful for DB maintenance)
13.Stored procedures should not be named with prefix “sp_”
14.Check is values for table audit columns (like createddate, createdby, updatedate, updatedby, isdeleted, deleteddate, deletedby etc.) are populated properly
15.Check if input data is not truncated while saving. Field length shown to user on page and in database schema should be same
16.Check numeric fields with minimum, maximum, and float values
17.Check numeric fields with negative values (for both acceptance and non-acceptance)
18.Check if radio button and dropdown list options are saved correctly in database
19.Check if database fields are designed with correct data type and data length
20.Check if all table constraints like Primary key, Foreign key etc. are implemented correctly
21.Test stored procedures and triggers with sample input data
22.Input field leading and trailing spaces should be truncated before committing data to database
23.Null values should not be allowed for Primary key column
-----------------------------------------------------------------------------------------------------------------------
Payment Gateway Testing Checklist and Test Cases
1.Set up payment processor sandbox.2.Gather test credit card numbers that would be used for testing different credit cards. As an example, such information for Braintree payment processor can be found at Braintree payments.
3.Verify the behavior of the application when a transaction is successful.
4.After successful transaction verify if the payment gateway returns to your application to show some kind of successful transaction/confirmation message.
5.Verify that the customer gets some kind of transaction confirmation notification like Order confirmation email, etc. if the transaction is successful.
6.Check what happens if a payment fails or payment processor stops responding- is there any error message?
7.Verify the application behavior with browser popup blocker on and off. This may be helpful if any confirmation messages are being displayed in the popup.
8.Verify different fraud prevention/security settings.
For example, if customer billing information does not match with the address provided to issuing bank- any mismatch will result in transaction decline.
9.Verify the transaction entries in the database if the tester has access to the Application database.
10.Check what happens when a customer session expires.
11.Check the console during entire transaction and report any console errors that are observed.
12.Verify that that transaction is done on a secure channel.
For example, the checkout pages may be HTTPS versus rest of website that are HTTP pages.
13.Verify that the payment processor currency is setup correctly.
For example, if the application/website is a Canadian company/retailer, the payment processor should be set up to accept CAD currency.
14.If the applications have multiple payment options like Credit card and PayPal together, both payment options need to individually tested from end to end.
15.Verify that refund or void amount (from payment processor admin portal) is same as the transaction amount. In no case, the refund/void amount should exceed the transaction amount.
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios for Performance Testing
1.Check if page load time is within acceptable range2.Check page load on slow connections
3.Check response time for any action under light, normal, moderate and heavy load conditions
4.Check performance of database stored procedures and triggers
5.Check database query execution time
6.Check for load testing of application
7.Check for stress testing of application
8.Check CPU and memory usage under peak load
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios for Image Upload Functionality
1.Check for uploaded image path2.Check image upload and change functionality
3.Check image upload functionality with image files of different extensions (e.g. JPEG, PNG, BMP etc.)
4.Check image upload functionality with images having space or any other allowed special character in file name
5.Check duplicate name image upload
6.Check image upload with image size greater than the max allowed size. Proper error message should be displayed.
7.Check image upload functionality with file types other than images (e.g. txt, doc, pdf, exe etc.). Proper error message should be displayed
8.Check if images of specified height and width (if defined) are accepted otherwise rejected
9.Image upload progress bar should appear for large size images
10.Check if cancel button functionality is working in between upload process
11.Check if file selection dialog shows only supported files listed
12.Check multiple images upload functionality
13.Check image quality after upload. Image quality should not be changed after upload
14.Check if user is able to use/view the uploaded images
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios for Sending Emails
1.Email template should use standard CSS for all emails2.Email addresses should be validated before sending emails
3.Special characters in email body template should be handled properly
4.Language specific characters (e.g. Russian, Chinese or German language characters) should be handled properly in email body template
5.Email subject should not be blank
6.Placeholder fields used in email template should be replaced with actual values e.g. {Firstname} {Lastname} should be replaced with individuals first and last name properly for all recipients
7.If reports with dynamic values are included in email body, report data should be calculated correctly
8.Email sender name should not be blank
9.Emails should be checked in different email clients like Outlook, Gmail, Hotmail, Yahoo! mail etc.
10.Check send email functionality using TO, CC and BCC fields
11.Check plain text emails
12.Check HTML format emails
13.Check email header and footer for company logo, privacy policy and other links
14.Check emails with attachments
15.Check send email functionality to single, multiple or distribution list recipients
16.Check if reply to email address is correct
17.Check sending high volume of emails
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios for Excel Export Functionality
1.File should get exported in proper file extension2.File name for the exported Excel file should be as per the standards e.g. if file name is using timestamp, it should get replaced properly with actual timestamp at the time of exporting the file
3.Check for date format if exported Excel file contains date columns
4.Check number formatting for numeric or currency values. Formatting should be same as shown on page
5.Exported file should have columns with proper column names
6.Default page sorting should be carried in exported file as well
7.Excel file data should be formatted properly with header and footer text, date, page numbers etc. values for all pages
8.Check if data displayed on page and exported Excel file is same
9.Check export functionality when pagination is enabled
10.Check if export button is showing proper icon according to exported file type e.g. Excel file icon for xls files
11.Check export functionality for files with very large size
12.Check export functionality for pages containing special characters. Check if these special characters are exported properly in Excel file
-----------------------------------------------------------------------------------------------------------------------
Test Scenarios for Mobile Game Testing
1.Check for background music and sound effects2.ON/OFF sound & background music
3.Receive the call and check
4.Verify if sound effects are in sync with action
5.ON/OFF device sound(native sound) and check
6.Check for vibration effect if present
7.User Interface Check in Landscape/Portrait mode
8.Check for animation, movement of character, graphics, Zoom In/Out (all gestures) etc.
9.There should not be any clipping (cutted background)
10.Test whether one object overlaps with another
11.Verify if loading indicator is displayed wherever required
12.Character should not move out of the screen/specified area
13.Test for enable and disable images/icons/buttons etc.
14.Check for screen title
15.Check for message title, message description, label (should be appropriate)
16.Check scrolling
17.Font displayed (color, size etc.)
18.Check other objects too (ex -if it’s a car race- you need to look at road, people, other objects like buildings etc.)
19.Performance Check the loading time of a game
20.Make sure that any action is not taking considerable time, game flow should be fast
21.Multitasking Switch b/w different apps and play game , check for sound, score, UI, time-out etc.
22.Pause&Check if game is paused when call received or multitasking or sleep mode
23.Save Settings Turnoff and ON device, check if settings are saved
24.Log out /On , check same
25.User should not loose his game in above conditions
Test Scenarios for User profile
1.Put an all types of images in Player profile and check2.Put special character, numbers, space in username and check
3.Password should be in masked
Test Scenarios for Chat feature
1.Check the profile images2.max limit of chat description
3.Enter empty string, special character and check
4.For an opponent,there should be a notification that he has received a message
Test scenarios for Functionality
1.Check game area, game logic2.play till last level
3.get the cheat codes from development team and check all the levels
4.Check for the features that will be unlocked level-wise
5.Check for bonus score
6.Check the score hike when level gets increased
7.Check for multi-tap action (example in a car race we hold accelerator and left/right turn button simultaneously)
8.Check Menu options
9.Check Different game modes/location
10.Check Help & About Screen is in easily understandable format
11.free from spelling mistakes
12.URL should be hyperlinked (depends)
Test Scenarios for Multiplayer game
1.Session expiry check2.login/log out
3.Registration (Sign Up)
4.Verify account (receive verification mail)
5.login with registered but not verified account (without clicking verification link)
6.Forgot password checks (many cases here)
7.Game flow
8.Check for WIN/lost/Draw
9.Check user statistics graph
10.Challenge/Decline challenge/receive challenge
11.Check for forfeit
12.Check when player 2’s turn is on Player 1 is not able to do actions (should not be able to forfeit also)
13.Check for pass turn
14.Check for time-out (for one player)
15.Check the score for both the players till game ends
16.Memory leak Check the game when device memory is low
17.Network (n/w) check N/w messages if n/w is not present
18.Check if what happens when n/w not present and user plays a move (whether score submitted for that move etc.)
19.Check for localization-Should be Support of different languages
20.Check for time format-Change the device time,format etc.
21.Size-User won’t like if your game takes lot of device space, so keep one eye on game file size
22.Device,OS-Check in supported screen sizes and os versions (basically depend upon Client requirement)
23.Depends on platform Sometime we need to check as per OS guidelines as well. For ex in Wp7 we need to check in 2 background (light/dark).
24.Check Share options Post score via mail/FB/Twitter
25.Check the posted/sent messages in FB/Twitter/Mail. Check links are hyperlinked and application icon is displayed in
the post (depends)
26.If twitter integration is a manual ( custom UI developed by developer), check what happens when u enter more than
140 chars (as twitter limit is 140)
Test Music playing during app launch-If music player running and we start installing any game app, music player should pause without prompting for the user permission.
Steps for checking this:
1.Play a music file.2.Launch the application.
3. Verify that while the application loads, it does not pause, resume or stop the actively playing music.
4.Interruption If app (game) is in running mode, then Check the behavior of interruption like Bluetooth, Infra-red and CALL/SMS/MMS.
5.Upgrade the game/Battery effect-Upgrade of Games to the latest version and while migration all data should persist [score, user profile etc.]
6.What if Battery goes down/switched of the cell while playing, Whether the score will get saved?
Test Scenarios for score calculation
1.Verify leader-boards General/All time/Weekly/local etc.2.Check the score registration functionality
3.Check the format (whether, comma is required in score etc. ideally if customer is a foreigner coma should be in millions not in thousands )
4.Check for level completion syncs with the score
5.Check for time out
6.Do the actions when time-out yet to happen
For Part1 view this link
http://somustest.blogspot.com/2018/05/test-scenarios-for-some-general-things.html
No comments:
Post a Comment