Friday, May 25, 2018

Test Scenarios for some General things asked in interview-part1

Test Scenarios of Pen

1.Verify the type of pen- whether it is ball point pen, ink pen or gel pen
2.Verify the outer body of the pen- whether it should be metallic, plastic or any other material as per the specification
3.Verify that length, breadth and other size specifications of the pen
4.Verify the weight of the pen
5.Verify if the pen is with cap or without cap
6.Verify if the pen has rubber grip or not
7.Verify the color of the ink of the pen
8.Verify the odour of the pen
9.Verify the size of the tip of the pen
10.Verify the company name or logo of the maker is correct and at desired place
11.Verify if the pen is smooth
12.Verify if the pen's ink gets leaked in case it is tilted upside down
13.Verify if the pen's gets leaked at higher altitude
14.Verify the type of surfaces the pen can write at
15.Verify if the text written by pen is erasable or not
16.Verify pen's and its ink condition at extreme temperature is as per the specification
17.Verify the pressure up to which the pen's tip can resist and work correctly
18.Verify the pen is breakable or not at a certain height as the specification
19.Verify text written by pen doesn't get faded before a certain time as per the specification
20.Verify the effect of water, oil and other liquid on the text written by pen
21.Verify the condition of ink after long period of time is as per permissible specification or not
22.Verify the total amount of text that can be written by the pen at one go
23.Verify the pen's ink is waterproof or not
24.Verify if the pen is able to write when used against the gravity- upside down
25.Verify that in case of ink pen, the pen's ink can be refilled again
------------------------------------------------------------------------------------------------------------------------------

Test cases Of Pencil

1.Verify that the text written with pencil is legible
2.Verify that the writing with pencil is smooth on different type/quality of paper surfaces
3.Check that the darkness/color of the text written by pencil is as per the specifications
4.Check the strength of the lead, it should not break when a specified(normal human) pressure is applied
5.Verify that the text written by pencil can be erased by normal erasers
6.Verify that the quality and strength of the pencil's wood
7.Check whether the outer body of pencil is circular or some polygon shape
8.Verify that the length and radius of the pencil is as per the specification
9.Verify that the weight of the application is as per the specification
10.Verify that the pencil can be sharpened easily by normal sharpener
11.Verify the total length of text written by a complete pencil
12.Verify the total length of text written before need to sharpen the pencil again
13.Verify that the pencil writes on the normal specified surfaces clearly
14.Verify the outer coloring of pencil's paint
15.Check if pencil writes when put in water for some time
16.Check the quality and strength of pencil when immersed in water for some time
17.Check that the text written by pencil gets erased or note when the paper is immersed in water and later dried
------------------------------------------------------------------------------------------------------------------------------

Security Testing Test Scenarios

1.Check for SQL injection attacks
2.Secure pages should use HTTPS protocol
3.Page crash should not reveal application or server info. Error page should be displayed for this
4.Escape special characters in input
5.Error messages should not reveal any sensitive information
6.All credentials should be transferred over an encrypted channel
7.Test password security and password policy enforcement
8.Check application logout functionality
9.Check for Brute Force Attacks
10.Cookie information should be stored in encrypted format only
11.Check session cookie duration and session termination after timeout or logout
12.Session tokens should be transmitted over secured channel
13.Password should not be stored in cookies
14.Test for Denial of Service attacks
15.Test for memory leakage
16.Test unauthorized application access by manipulating variable values in browser address bar
17.Test file extension handing so that exe files are not uploaded and executed on server
18.Sensitive fields like passwords and credit card information should not have auto complete enabled
19.File upload functionality should use file type restrictions and also anti-virus for scanning uploaded files
20.Check if directory listing is prohibited
21.Password and other sensitive fields should be masked while typing
22.Check if forgot password functionality is secured with features like temporary password expiry after specified hours and security question is asked before changing or requesting new password
23.Verify CAPTCHA functionality
24.Check if important events are logged in log files
25.Check if access privileges are implemented correctly
Test Scenarios of ATM Machine
1.Verify the slot for ATM Card insertion is as per the specification
2.Verify that user is presented with options when card is inserted from proper side
3.Verify that no option to continue and enter credentials is displayed to user when card is inserted correctly
4.Verify that font of the text displayed in ATM screen is as per the specifications
5.Verify that touch of the ATM screen is smooth and operational
6.Verify that user is presented with option to choose language for further operations
7.Verify that user asked to enter pin number before displaying any card/bank account detail
8.Verify that there are limited number of attempts up to which user is allowed to enter pin code
9.Verify that if total number of incorrect pin attempts gets surpassed then user is not allowed to continue further- operations like blocking of card etc. gets initiated
10.Verify that pin is encrypted and when entered
11.Verify that user is presented with different account type options like- saving, current etc.
12.Verify that user is allowed to get account details like available balance
13.Verify that user same amount of money gets dispatched as entered by user for cash withdrawal
14.Verify that user is only allowed to enter amount in multiples of denominations as per the specifications
15.Verify that user is prompted to enter the amount again in case amount entered is not as per the specification and proper message should be displayed for the same
16.Verify that user cannot fetch more amount than the total available balance
17.Verify that user is provided the option to print the transaction/enquiry
18.Verify that user user's session timeout is maintained and is as per the specifications
19.Verify that user is not allowed to exceed one transaction limit amount
20.Verify that user is not allowed to exceed one day transaction limit amount
21.Verify that user is allowed to do only one transaction per pin request
22.Verify that user is not allowed to proceed with expired ATM card
23.Verify that in case ATM machine runs out of money, proper message is displayed to user
24.Verify that in case sudden electricity loss in between the operation, the transaction is marked as null and amount is not withdrawn from user's account
---------------------------------------------------------------------------------------------------------------------

Test scenarios of Bike

1.Verify that design and dimension of the application are as per the specifications
2.Verify that the different colors used in the bike are of the correct shades as per the specifications
3.Verify that the weight of the bike is as per the specifications
4.Check the material used in different parts of bike - outer body, tyres, seat etc.
Positive Test scenarios
1.Check if the bike is of type electric start, manual start or both
2.Verify that the bike starts smoothly using the available options
3.Check the amount of force to kick-start the bike
4.Verify that bike runs smoothly and attain desired speed when accelerated
5.Verify that the maximum speed attained by bike is as per the specification
6.Verify that the maximum acceleration attained by bike is as per the specification
7.Verify that noise made by bike is within the acceptable decibel levels
8.Verify that both the brakes work correctly
9.Verify that clutch works correctly
10.Check the number of gears in bike
11.Verify that user can change the gear from lower to higher
12.Verify that user can change the gear from higher to lower
13.Verify that bike can be ridden on all types of road surfaces - charcoal, cement, wet road etc.
14.Verify that bike can be ridden on all weather conditions
15.Verify that bike can be ridden on slop and ramp
16.Verify the mileage of the bike is as per the specification when driven on standard surface
17.Check the pick-up of the bike
18.Check the fuel tank capacity of the bike
19.Check the fuel type requirement
20.Verify that the pollution is within the permissible limit
21.Verify that the fuel meter displays correct status of fuel
22.Verify that speedometer displays correct speed of the bike
23.Verify that the dashboard displays all the information correctly
24.Verify that indicators and indicator light works correctly
25.Verify that the headlight work correctly
26.Check if bike has reserve oil or not
27.Verify that horn works correctly
-------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Car

Positive Test Cases of Car

1.Verify that car should get unlocked and start smoothly on unlocking with its key
2.Verify that car gets driven smoothly at normal speed on road and under normal climatic condition
3.Verify that clutch, break and accelerator functions are working correctly
4.Verify the engine type of car - whether it is Petrol, Diesel or CNG engine
5.Verify the car's performance on different types of roads- charcoal, cement etc.
6.Verify car's performance and fuel consumption on plains, hills and slops
7.Verify that the mileage of the car is as per the specification
8.Verify that the dimensions of the car are as per the specification
9.Check if the car is sports car or luxury car
10.Check that the fuel capacity is as per the specification
11.Check if the steering is power steering or not
12.Check if gears are automatic or manual
13.Verify if the reverse gear of the car works correctly
14.Check if the height of the car's floor is at an optimum distance from road
15.Verify the top speed of the car under normal conditions
16.Verify the maximum acceleration of the car
17.Verify the car's outer body material
18.Check if the car's pane are made of tempered glass or not
19.Check the number of seats in the car
20.Check if the hand brakes are functional or not
21.Verify that brakes work correctly and gets applied in a timely manner or not
22.Verify the type and power of battery
23.Check if the headlights are working fine and give proper lighting when applied at night/dark
24.Verify the shock absorber of the car
25.Verify if the air bags are present or not and are functional if present
26.Check if center locking is present or not and is functional if present
27.Check if the seat belts are present and are functioning correctly
28.Verify car's interior- spacing, material, quality etc.
29.Verify if the speedometer, fuel meter and other indicators are working fine or not
30.Verify cars performance, tyre's grip on driving the car on rainy day
31.Verify that car should get started and run smoothly on using it after several days
32.Check the automatic car lock functionality
33.Verify that car's back light should get lightened on reversing the car
34.Verify that left and right indicators should function correctly
35.Check if anti-theft alarm is working correctly or not

Negative Test Cases of Car

1.Verify the car's functioning on filling it with non-prescribed fuel type
2.Drive car at high speed on first gear only
3.Keep the air pressure different on all the four tyres and then drive the car
4.Use hand break while driving the car
5.Try to start the car with some other key
6.Check the condition of tyres on filling them at pressure higher than prescribed
7.Check the condition, speed and fuel consumption of car on filling the tyres with pressure less than prescribed
8.Check car's speed, performance and fuel consumption on driving the car on roads not conducive for driving
--------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Calculator

1.Check if the calculator is normal calculator or scientific calculator
2.Verify that all the buttons are present and text written on them is readable
3.Check the arithmetic operations are working fine- +, -, /, * etc.
4.Verify that BODMAS is applied in case of complex queries and correct result is returned
5.Verify that calculator gives correct result in case of operations containing decimal numbers
6.Check if the calculator is battery operated or works on solar power
7.Verify the outer body material of the calculator
8.Verify the spacing between the two buttons, the buttons should not be too closely placed
9.Check the pressure required to press a button, the pressure required should not be too high
10.Verify the number of digits allowed to enter in the calculator for any operation
11.Verify the limit of the response value
12.Verify the functioning of memory functions
13.Check if calculator allows to navigate through previous calculations
14.Verify that hitting 'C' cancels any digits or operation added
15.Verify the working of ON-OFF button in the calculator
16.Check if keeping the calculator unused for certain period of time, turns it off automatically
17.Verify that on pressing two operators one after the other, the latest one will override the previous operator
18.Verify the state of calculator when two buttons are pressed simultaneously
19.Verify if user can delete a digits one by one using backspace key
---------------------------------------------------------------------------------------------------------------------------

Test Scenarios for Chair

1.Verify that the chair is stable enough to take an average human load
2.Check the material used in making the chair-wood, plastic etc.
3.Check if the chair's leg are level to the floor
4.Check the usability of the chair as an office chair, normal household chair
5.Check if there is back support in the chair
6.Check if there is support for hands in the chair
7.Verify the paint's type and color
8.Verify if the chair's material is brittle or not
9.Check if cushion is provided with chair or not
10.Check the condition when washed with water or effect of water on chair
11.Verify that the dimension of chair is as per the specifications
12.Verify that the weight of the chair is as per the specifications
13.Check the height of the chair's seat from floor
-----------------------------------------------------------------------------------------------------------------------------

Test cases of Coffee Machine

1.UI scenario - Verify that the dimension of the coffee machine are as per the specification
2.Verify that outer body as well as inner part's material are as per the specification
3.Verify that the machine's body color as well brand are correctly visible and as per specification
4.Verify the input mechanism for coffee ingredients-milk, water, coffee beans/powder etc.
5.Verify that the quantity of hot water, milk, coffee powder per serving is correct
6.Verify the power/voltage requirements of the machine
7.Verify the effect of suddenly switching off the machine or cutting the power. Machine should stop in that situation and in power resumption, the remaining coffee should not get come out of the nozzle.
8.Verify that coffee should not leak when not in operation
9.Verify the amount of coffee served in single serving is as per specification
10.Verify that the digital display displays correct information
11.Check if the machine can be switched on and off using the power buttons
12.Check for the indicator lights when machine is switched on-off
13.Verify that the functioning of all the buttons work properly when pressed
14.Verify that each button has image/text with it, indicating the task it performs
15.Verify that complete quantity of coffee should get poured in single operation, no residual coffee should be present in the nozzle
16.Verify the mechanism to clean the system work correctly- foamer
17.Verify that the coffee served has the same and correct temperature each time it is served by the machine
18.Verify that system should display error when it runs out of ingredients
19.Verify that pressing coffee button multiple times lead to multiple serving of coffee
20.Verify that there is passage for residual/extra coffee in the machine
21.Verify that machine should work correctly in different climatic, moistures and temperature conditions
22.Verify that machine should not make too much sound when in operation
23.Performance test - Check the amount of time the machine takes to serve a single serving of coffee
24.Performance test - Check the performance of the machine when used continuously till the ingredients run out of the requirements
25.Negative Test - Check the functioning of coffee machine when two/multiple buttons are pressed simultaneously
26.Negative Test - Check the functioning of coffee machine with lesser or higher voltage then required
27.Negative Test - Check the functioning of coffee machine if the ingredient container's capacity is exceeded
-------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Date field

1.Verify that on clicking the date field a calendar widget should open.
2.Verify that the default width of the calendar should be displayed as per the specification.
3.Verify that user can select a date in the calendar and after selecting the date the same gets displayed in the date field.
4.Verify that by default current month's calendar should be displayed.
5.Verify that user can move to previous and next month's calendar by choosing the left and right icon over the calendar.
6.Verify that user can check a specific year's calendar.
7.Verify that user enter date manually in the date following the date format.
8.Verify that user can edit a date set by choosing the one selected from the calendar.
9.Verify that values other than numeric’s should not be allowed in the date field (apart from the characters used in the date format like '/' or '-'.
10.Verify that invalid dates are not allowed in the date field (like date value exceeding 31, month value exceeding 12 etc.).
--------------------------------------------------------------------------------------------------------------------------------

Test cases of Door

1.Verify if the door is single door or bi-folded door
2.Check if the door opens inwards or outwards
3.Verify that the dimension of the doors are as per the specifications
4.Verify that the material used in the door body and its parts is as per the specifications
5.Verify that color of the door is as specified
6.Verify if the door is sliding door or rotating door
7.Check the position, quality and strength of hinges
8.Check the type of locks in the door
9.Check the number of locks in the door interior side or exterior side
10.Verify if the door is having peek-hole or not
11.Verify if the door is having stopper or not
12.Verify if the door closes automatically or not - spring mechanism
13.Verify if the door makes noise when opened or closed
14.Check the door condition when used extensively with water
15.Check the door condition in different climatic conditions- temperature, humidity etc.
16.Check the amount of force- pull or push required to open or close the door
-------------------------------------------------------------------------------------------------------------------------------

Test cases for online Shopping Application

Some high level test cases of an e-commerce website covering general UI test cases, product buy flow test cases and product creation panel test cases.

General Test Cases

1.Verify that user is able to navigate through all the products across different categories
2.Verify that all the links and banners are redirecting to correct product/category pages and none of the links are broken
3.Verify that the company logo is clearly visible
4.Verify that all the text - product, category name, price and product description are clearly visible
5.Verify that all the images - product and banner are clearly visible
6.Verify that category pages have relevant product listed specific to the category
7.Verify that correct count of total products are listed on the category pages
8.Search - Verify that on searching all the product satisfying the search criteria are visible on the search result page
9.Search - Verify the more relevant product for the search term are displayed on the top for a particular search term
10.Search - Verify that count of products is correctly displayed on the search result page for a particular search term
11.Filtering - Verify that filtering functionality correctly filters product based on the filter applied
12.Filtering - Verify that filtering works correctly on category pages
13.Filtering - Verify that filtering works correctly on the search result page
14.Filtering - Verify that correct count of total products is displayed after a filter is applied
15.Sorting - Verify that all the sort options work correctly - correctly sort the products based on the sort option chosen
16.Sorting - Verify that sorting works correctly on the category pages
17.Sorting - Verify that sorting works correctly on the search result page
18.Sorting - Verify that sorting works correctly on the pages containing filtered result, after applying filters
19.Sorting - Verify that product count remains intact irrespective of sorting option applied

Product Buy Flow - Test cases

1.Verify that on the product page, user can select the desired attribute of the product e.g. size, color etc.
2.Verify that user can add to cart one or more products
3.Verify that user can add products to wish list
4.Verify that user can buy products added to cart after signing in to the application (or as per the functionality of the website)
5.Verify that user can successfully buy more than one products that were added to his/her cart
6.Verify that user cannot add more than available inventory of the product
7.Verify that the limit to the number of products a user can by is working correctly by displaying error message and preventing user from buying more than the limit
8.Verify that the delivery can be declined of for the places where shipping is not available
9.Verify that Cash on Delivery option of payment is working fine
10.Verify that the different prepaid methods of payments are working fine
11.Verify that product return functionality works fine

User (Buyer) Registration - Test cases

1.Verify that all the specified fields are present on the registration page
2.Verify that the required/mandatory fields are marked with * against the field
3.Verify that for better user interface drop downs, radio buttons and check boxes etc. fields are displayed wherever possible instead of just textboxes
4.Verify the page has both submit and cancel/reset buttons at the end
5.Verify that clicking submit button after entering all the required fields, submits the data to the server
6.Verify that clicking cancel/reset button after entering all the required fields, cancels the submit request and resets all the fields
7.Verify that whenever possible validation should take place at client side
8.Verify that not filling the mandatory fields and clicking submit button will lead to validation error
9.Verify that not filling the optional fields and clicking submit button will still send data to server without any validation error
10.Check the upper limit of the text boxes
11.Check validation on date and email fields (only valid dates and valid email Ids should be allowed
12.Check validation on numeric fields by entering alphabets and special characters
13.Verify that leading and trailing spaces are trimmed
14.Verify that entering blank spaces on mandatory fields lead to validation error
15.Verify that after making a request to the server and then sending the same request again with the same unique key will lead to server side validation error

Seller - Product creation Test cases

1.Verify that authenticated sellers get access to product creation panel specific to the authorized categories
2.Verify that product creation panel is working fine for single product creation
3.Verify that product creation panel is working fine for multiple product creation
4.Verify that maximum product creation limit for seller is working fine, limiting seller to create more than the desired number of products
5.Verify panel validation for checking mandatory fields
6.Verify that duplicate product creation is restricted through panel
7.Verify that seller can update information and price of existing products
8.Verify that product created by seller get visible on the website after certain period of time
9.Verify that updating made by seller get visible on the website after certain period of time
----------------------------------------------------------------------------------------------------------------------

Test Scenarios of Facebook

Some test scenarios of Facebook. Although there would be thousands of test cases for facebook but we are limiting the tests to common features like - profile setting, comments and post in timeline etc. We will leave features like creating signup, login, page creation, group’s creation, events etc. Please note that the below mentioned scenarios are for reference only to teach the concept of test scenario writing, the tests are nowhere related to actual Facebook's testing.
For login and registration functionality check Test Scenarios for Login and Test Scenarios for Registration.

Facebook User Timeline Scenarios

1.Verify that user can set profile pic uploaded from his or her computer.
2.Verify that user can set profile pic uploaded from mobile.
3.Verify that user can set profile pic from photos present on his facbook account's photo section.
4.Verify that user can set profile from webcam or mobile camera.
5.Verify that user can set cover pic uploaded from his or her computer.
6.Verify that user can set cover pic uploaded from mobile.
7.Verify that user can set cover pic from photos present on his facbook account's photo section.
8.Verify that user can set cover from webcam or mobile camera.
9.Verify that uploading image of unsupported type should lead to error message.
10.Verify that uploading image of size exceeding maximum allowed size should lead to error message.
11.Verify that uploading image of size less than the allowed minimum size should lead to error message.
12.Verify that uploading image of larger dimension than permitted should lead to error message.
13.Verify that uploading image of smaller dimension than permitted should lead to error message.
14.Verify that change in profile pic should get reflected in each post/comment of the user's timeline.
15.Verify that user can add/edit their account information displayed to other users.
16.Verify that users can post text in their timeline and the same gets displayed to their friends.
17.Verify that users can post images in their timeline and the same gets displayed to their friends.
18.Verify that users can post links with or without preview in their timeline and the same gets displayed to their friends.
19.Verify that user can tag friends in their posts.
20.Verify that users can see the all the post in their timeline.
21.Verify that users can see comments, likes and reactions in the posts present in their timeline.
22.Verify that users can post comments, like and react to the posts present in their timeline.

Friends and their Timelines Scenario

1.Verify that user can search for friends in facebook's 'Find friends' search functionality.
2.Verify that user can send friend request to any user by visiting their page.
3.Verify that user can navigate through their Friend's friend and send friend request to them.
4.Verify that user can approve or decline received friend request.
5.Verify that user can unfriend any existing friend.
6.Verify that users can see timeline of their friends.
7.Verify that users can post text in their friend's timeline.
8.Verify that users can post images in their timeline and the same gets displayed to their friends.
9.Verify that users can post links with or without preview in their friend's timeline.
10.Verify that user can tag friends in their posts on friend's timeline.
11.Verify that users can see the all the post in their friend's timeline.
12.Verify that users can see comments, likes and reactions in the posts present in their friend's timeline.
13.Verify that users can post comments, like and react to the posts present in their friend's timeline.

Facebook Notification Test Scenarios

1.Verify that users receive different notifications on facebook 'Notifications' icon.
2.Verify that users receive different notifications on email or cell phone based on the settings chosen when not logged in to facebook.
3.Verify that users receive notification when their friend request gets approved.
4.Verify that users receive notification when they get friend request.
5.Verify that users receive notification when they get tagged by someone on posts or comments.
6.Verify that users receive notification when they get comments, like or reactions on their posts.
7.Verify that users receive notification when someone posts on their timeline.
----------------------------------------------------------------------------------------------------------------------------------

Test Scenarios Login Page

1.Verify that the login screen is having option to enter username and password with submit button and option of forgot password
2.Verify that user is able to login with valid username and password
3.Verify that user is not able to login with invalid username and password
4.Verify that validation message gets displayed in case user leaves username or password field as blank
5.Verify that validation message is displayed in case user exceeds the character limit of the user name and password fields
6.Verify that there is reset button to clear the field's text
7.Verify if there is checkbox with label "remember password" in the login page
8.Verify that the password is in encrypted form when entered
9.Verify that there is limit on the total number of unsuccessful attempts
10.For security point of view, in case of in correct credentials user is displayed the message like "incorrect username or password" instead of exact message pointing at the field that is incorrect. As message like "incorrect username" will aid hacker in brute forcing the fields one by one
11.Verify the timeout of the login session
12.Verify if the password can be copy-pasted or not
13.Verify that once logged in, clicking back button doesn't logout user
14.Verify if SQL Injection attacks works on login page
15.Verify if XSS vulnerability work on login page
---------------------------------------------------------------------------------------------------------------------------------

Test scenarios for Registration Page

1.Verify that all the specified fields are present on the registration page
2.Verify that the required/mandatory fields are marked with * against the field
3.Verify that for better user interface dropdowns, radio buttons and checkboxes etc. fields are displayed wherever possible instead of just textboxes
4.Verify the page has both submit and cancel/reset buttons at the end
5.Verify that clicking submit button after entering all the required fields, submits the data to the server
6.Verify that clicking cancel/reset button after entering all the required fields, cancels the submit request and resets all the fields
7.Verify that whenever possible validation should take place at client side
8.Verify that not filling the mandatory fields and clicking submit button will lead to validation error
9.Verify that not filling the optional fields and clicking submit button will still send data to server without any validation error
10.Check the upper limit of the textboxes
11.Check validation on date and email fields (only valid dates and valid email Ids should be allowed
12.Check validation on numeric fields by entering alphabets and special characters
13.Verify that leading and trailing spaces are trimmed
14.Verify that entering blank spaces on mandatory fields lead to validation error
15.Verify that after making a request to the server and then sending the same request again with the same unique key will lead to server side validation error
---------------------------------------------------------------------------------------------------------------------------------

Test scenarios for Fan

1.Check the type of fan - whether the fan is ceiling fan or table fan
2.Verify the number of blades on the fan
3.Verify the ON-OFF functionality of fan
4.Verify if the fan works normally-throws wind on the right direction
5.Verify the material of which fan's blade and other parts are made
6.Check the voltage/power requirement of the fan
7.Verify the maximum speed of fan
8.Check the minimum speed of the fan
9.Verify that the speed of fan can be regulated using regulator
10.Verify that when in motion, the fan should not wobble
11.Check the length of the fan rod and blades
12.Verify that the weight of the fan is as per the specifications
13.Verify that the color of the fan is as per the specifications
14.Check the effect of voltage fluctuation on fan when in motion
15.Check the effect of sudden electricity outage on fan's motor and other electrical parts
16.Verify the fan's condition when continuously switched on for very large duration
17.Check if there is any life time of fan's internal parts or the body
18.Check if the blades of the fan can be bend or not, check if its material is brittle
19.Check the time taken by fan to attain maximum speed, when switched ON
---------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Flight Reservation System

1.Verify that there is portal to add new flights in the system.
2.Verify that on filling flight details like flight name, code, from and to destinations, capacity, timings and frequency etc., new flights get successfully added in the system.
3.Verify that user can search for flights by name, from-to airports or flight code for checking their status and timings.
4.Verify that search results have flight details, timings and availability.
5.Verify that clicking the search results open complete details for flight.
6.Verify that user should see real time flight status of availability of seats.
7.Verify that user is presented with graphical view of the airline's sitting arrangement along with seat number and availability status.
8.Verify that pricing of different types of seats is displayed to the users.
9.Verify that user can successfully select single or more than one seat.
10.Verify that user cannot select or is not permitted to select seats that are already booked or not allowed for booking.
11.Verify that after selecting seats, entering passenger details and making payment the selected seats get booked.
12.Verify that on successful booking the ticket should be visible and downloadable.
13.Verify that after successful booking the seat's status is updated to booked.
14.Verify that user also receive confirmation mail along with tickets on the email IDs provided while filling the details.
15.Verify the maximum limit of seats that a user can book, selecting more seats than permitted results in error message.
16.Verify that all the different types of payment methods work fine.
17.Verify that user is presented with additional options like- luggage, extra leg room, foods/beverages etc. and selecting the same results in additional cost with the booking amount.
18.Verify that user can also cancel the tickets booked by entering the mandatory details and the amount after deducting the cancellation fee gets refunded back to user.
19.Verify that after cancellation the seat's status is updated to available.
---------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Gmail

Test Scenarios for Inbox Functionality (Receive Email)

1.Verify that a newly received email is displayed as highlighted in the Inbox section.
2.Verify that a newly received email has correctly displayed sender email ID or name, mail subject and mail body (trimmed to single line).
3.Verify that on clicking the newly received email, user is navigated to email content.
4.Verify that the email contents are correctly displayed with the desired source formatting.
5.Verify that any attachments are attached to the email and is downloadable.
6.Verify that the attachments are scanned for viruses before download.
7.Verify that all the emails marked as read are not highlighted.
8.Verify that all the emails read as well as unread have a mail read time appended at the end on the email list displayed in the inbox section.
9.Verify that count of unread emails is displayed alongside 'Inbox' text in left sidebar of Gmail.
10.Verify that unread email count increases by one on receiving a new email.
11.Verify that unread email count decreases by one on reading an email (marking email as read).
12.Verify that email recipients in cc are visible to all user.
13.Verify that email recipients in bcc are not visible to user.
14.Verify that all received emails get piled up in the 'Inbox' section and gets deleted in cyclic fashion based on the size availability.
15.Verify that email can be received from non-Gmail email IDs like - yahoo, Hotmail etc.

Test scenarios for Compose mail Functionality

1.Verify that on clicking 'Compose' button, a frame to compose a mail gets displayed.
2.Verify that user can enter email IDs in 'To', 'cc' and 'bcc' sections and also user will get suggestions while typing the email IDs based on the existing email IDs in user's email list.
3.Verify that user can enter multiple comma separated email IDs in 'To', 'cc' and 'bcc' sections.
4.Verify that user can type Subject line in the 'Subject' textbox.
5.Verify that user can type the email in email-body section.
6.Verify that user can format mail using editor-options provided like choosing font-family, font-size, bold-italic-underline etc.
7.Verify that user can user can attach file as an attachment to the email.
8.Verify that user can add images in the email and select the size for the same.
9.Verify that after entering email IDs in either of the 'To', 'cc' and 'bcc' sections, entering Subject line and mail body and clicking 'Send' button, mail gets delivered to intended receivers.
10.Verify that sent mails can be found in 'Sent Mail' sections of the sender.
11.Verify that mail can be sent to non-Gmail email IDs also.
12.Verify that all sent emails get piled up in the 'Sent Mail' section and gets deleted in cyclic fashion based on the size availability.
13.Verify that the emails composed but not sent remain in the draft section.
14.Verify the maximum number of email recipients that can be entered in 'To', 'cc' and 'bcc' sections.
15.Verify the maximum length of text that can be entered in the 'Subject' textbox.
16.Verify the content limit of text/images that can be entered and successfully delivered as mail body.
17.Verify the maximum size and number of attachment that can be attached with an email.
18.Verify that only the allowed specifications of the attachment can be attached with an email/
19.Verify that if email is sent without Subject, a pop-up is generated warning user about no subject line. Also, verify that on accepting the pop-up message, user is able to send the email.
-----------------------------------------------------------------------------------------------------------------------------

Test scenarios of Google Search

1.Verify that the response fetched for a particular keyword is correct and related to the keyword, containing links to the particular webpage
2.Verify that the response are sorted by relevancy in descending order i.e. most relevant result for the keyword are displayed on top
3.Verify that response for multi word keyword is correct
4.Verify that response for keywords containing alphanumeric and special characters is correct
5.Verify that the link title, URL and description have the keyword highlighted in the response
6.Verify auto-suggestion in Google e.g. providing input as 'fac' should give suggestions like 'Facebook', 'Facebook messenger', 'Facebook chat' etc.
7.Verify that response fetched on selecting the suggested keyword and on providing the keyword directly should be same
8.Verify that the suggestion provided by Google are sorted by most popular/relevant suggestions
9.Verify that user can make search corresponding to different categories - web, images, videos, news, books etc. and response should correspond to the keyword in that category only
10.Verify that misspelled keyword should get corrected and response corresponding to the correct keyword should get displayed
11.Verify that multi word misspelled keywords also get corrected
12.Verify the performance of search- check if the time taken to fetch the response is within the ballpark
13.Verify that total number of results fetched for a keyword
14.Verify that the search response should be localized that is response should be more relevant to the country/area from which the search request is initiated
15.Verify Google calculator service- make any arithmetic request, calculator should get displayed with correct result
16.Verify Google converter service- make request like- 10USD in INR and check if the result is correct
17.Verify search response for a large but valid strings
18.Verify that incorrect keywords - keywords not having related result should lead to "did not match any documents" response
19.Verify that user can make search using different languages
20.Verify that for a keywords, some related search terms are also displayed to aid user's search
21.Verify that for number of results more than the limit on a single page, pagination should be present, clicking on which user can navigate to subsequent page's result
22.Verify Google's advanced search options like- searching within a website, searching for files of specific extension
23.Verify if the search is case-insensitive or not
24.Verify the functionality of "I'm feeling Lucky" search- the top most search result should get directly returned (but as of now google doodle page link is displayed)

Front End - UI Test Cases of Google Search

1.Verify that Google Logo is present and center aligned
2.Verify that the search textbox is center aligned and editable
3.Verify that search request should get hit by clicking on search button or hitting enter after writing the search term
4.Verify that in the search result- webpage's title, URL and description are present
5.Verify that clicking the search result will lead to the corresponding web page
6.Verify that pagination is present in case number of results are greater than the maximum results allowed in a page
7.Verify that user can navigate to a page number directly or move to previous or next page using the links present
8.Verify that different languages links are present and gets applied on clicking the same
9.Verify that the total number of results for the keyword is displayed
10.Verify that the time taken to fetch the result is displayed
-------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Hospital Management System

1.Verify that the portal for new patient registration has all the mandatory fields required for registering a patient.
2.Verify that after filling the patient details and successful payment a Patient-Card is printed.
3.Verify that card has information like patient details, doctor assigned, department, application number, DOJ, bed allocated (if applicable) etc.
4.Verify that after patient checkup based on the requirement the details are updated in patient details database.
5.Verify that for existing patient based on application number of the patient, their records are added/updated in the database.
6.Verify that the system has an admin for doctors as well.
7.Verify that for each doctor’s details like their timings, specialty, fee, patient visited etc. is visible to the authorized users.
8.Verify that new details of new doctors can be added in the system.
9.Verify that details of existing users can be updated in the system.
10. Verify that doctor's record can be deleted from the system.
11.Verify the billing admin of the system calculates bill based on the patient's unique application number from the data generated from different systems.
12.Verify that the hard copy of the bill can be generating by printing the bill.
13.Verify that authorized users can also see total day wise billing done.
14.Verify the admin for hospital inventory, room and beds management.
15.Verify that the admin has the record of all the equipment’s, machines and medicines and the same gets updated when used or added to the system.
16.Verify that the admin has record of rooms and beds availability and same get updated based on their allotment and departure to patients.
-------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Keyboard

1.Check if all the keys- characters, numeric, function, special characters and arrow keys are present
2.Verify the ordering of the keys is as per the QWERTY standard
3.Check the functioning of each type of key-characters, numeric, function, special characters and arrow keys
4.Verify the working of the keys that work in combination like- shift+{other keys}
5.Check if the dimension of the key is as per the specification
6.Check the color of both keyboard body as well as the text written over the buttons
7.Check if the font type and size is as per the specification and legible
8.Check if the pressure required to press a key is not too high
9.Check the spacing between two keys, keys should not be congested and at the same time not too widely placed
10.Verify that in case of caps lock and other similar keys- an indicator lights glows
11.Check if keys doesn't make too much noise when clicked
12.Verify if the keyboard is wireless or wired keyboard
13.In case the keyboard is wireless, verify the range of keyboard
14.In case of wired keyboard, check the length of the keyboard
15.Verify if the keyboard contains multimedia functions as well
------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Kindle

1.Verify that the dimensions of the kindle device are as per the specifications.
2.Verify the screen resolution or the pixel density of the kindle.
3.Verify that eBooks are easily loaded in kindle.
4.Verify that the text written is easily readable.
5.Check the eBook format supported by the device - .azw, .azw3, .mobi, .txt etc.
6.Verify the number of eBooks that can be stored in the device or the size of the eBooks.
7.Check if the color of the device is as per the specifications or not.
8.Verify the quality of the kindle devices’ screen.
9.Check if the screen is anti-glare or not.
10.Check the font family supported by the device.
11.Check if there is option to increase font size or not and the functionality works correctly.
12.Check if there is option to change the screen brightness/contrast/sharpness and the functionality work correctly.
13.Check if the touch works fine or not.
14.Check the battery stand by time and performance when in use.
15.Check the network connectivity options - 3G or Wi-Fi.
16.Check if charging cable is provided with kindle or not.
17.Check the power requirement of the device.
------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Lift

1.Verify the dimensions of the lift
2.Verify the type of door of the lift is as per the specification
3.Verify the type of metal used in the lift interior and exterior
4.Verify the capacity of the lift in terms of total weight
5.Verify the buttons in the lift to close and open the door and numbers as per the number of floors
6.Verify that lift moves to the particular floor as the button of the floor is clicked
7.Verify that lift stops when up/down buttons at particular floor are pressed
8.Verify if there is any emergency button to contact officials in case of any mishap
9.Verify the performance of the floor - time taken to go to a floor
10.Verify that in case of power failure, lift doesn't free-fall and get halted in the particular floor
11.Verify lifts working in case button to open the door is pressed before reaching the destination floor
12.Verify that in case door is about to close and an object is placed between the doors, if the doors senses the object and again open or not
13.Verify the time duration for which door remain open by default
14.Verify if lift interior is having proper air ventilation
15.Verify lighting in the lift
16.Verify that at no point lifts door should open while in motion
17.Verify that in case of power loss, there should be a backup mechanism to safely get into a floor or a backup power supply
18.Verify that in case multiple floor number button are clicked, lift should stop at each floor
19.Verify that in case capacity limit is reached users are prompted with warning alert- audio/visual
20.Verify that inside lift users are prompted with current floor and direction information the lift is moving towards- audio/visual prompt
------------------------------------------------------------------------------------------------------------------------------

Test scenarios for Mobile Phone

Although there can be numerous test cases for mobile and considering smart phones, there can be even more test cases. But in this post we will focus mainly on- Calling, SMS and directory features.
1.Verify that all the required buttons- numbers 0-9, calling buttons etc. are present-
2.Verify that user can make a call by pressing numbers and hitting calling(green) button
3.Verify that user can make a call by selecting contact person from phone directory
4.Verify that user can reject an incoming call
5.Verify that user can receive an SMS
6.Verify that user can type and send an SMS
7.Verify that the dimension of the mobile is as per specification
8.Verify the screen size of the mobile
9.Verify that the weight of the mobile is as per the specification
10.Verify the font type and size of the characters printed on the keypad
11.Verify the color of the mobile phone's outer body and characters printed on keypad
12.Verify the pressure required to press a key on the keypad
13.Verify that spacing between the keys on the keypad are adequate
14.Check the type of mobile- smart phone or normal
15.Check if the mobile is colored or black-white
16.Check the lighting on the mobile screen is adequate- verify in dark daylight
17.Check if mobile phone can be locked out without password or pin
18.Check if mobile phone can be locked out with password or pin
19.Verify that mobile phone can be unlocked with/without password
20.Verify that user can receive call when phone is locked
21.Verify that receiving a call when phone is locked, doesn't unlocked it after call completion
22.Verify that user can select an incoming call and SMS alert ringtone
23.Verify that user can make silent or vibrate mode or incoming calls and SMS
24.Verify the battery requirement of the mobile
25.Verify the total time taken to charge the mobile completely
26.Verify the total time for mobile to get completely discharged when left idle
27.Verify the total talk for mobile to get completely discharged when continuously used in conversation
28.Verify the length of charger wire
29.Verify that mobile can be switched off and ON
30.Verify that user can store contact details on the phone book directory
31.Verify that user can delete and update contact details in the phonebook directory
32.Verify that Call logs are maintained in the Call Logs
33.Verify that received and Sent SMSs are saved in mobile
34.Verify that user can silent the phone during an incoming call
35.Verify the auto-reject option can be applied and removed on particular numbers 
------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Computer Mouse

1.Check if the mouse is optical mouse or not
2.Verify that left click and right click buttons are working fine
3.Check if double click is working fine
4.Verify the time duration between two left clicks, in order to consider it as double click
5.Check if scroller is present at the top or not
6.Verify the speed of mouse pointer
7.Check the pressure required for clicking the mouse buttons
8.Verify the acceleration of mouse pointer
9.Verify that clicking the button and dragging the mouse operation is working fine(drag and drop functionality)
10.Check the dimension of the mouse, if its suitable to grip and work
11.Verify that mouse works in all the allowed surfaces
12.Check if the mouse is wireless mouse or corded mouse
13.In case of wireless mouse, check the range up to which the mouse remains operational
14.In case of wireless mouse, check the battery requirement of the mouse
15.Check if there is option to switch on or mouse
------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Microwave Oven

1.Verify that the dimensions of the oven are as per the specification provided.
2.Verify that the oven's material is optimal for its use as oven and as per the specification.
3.Verify that the oven heats the food at desired temperature properly.
4.Verify that oven heats food at desired temperature within specified time duration.
5.Verify the ovens functioning with maximum attainable temperature.
6.Verify the ovens functioning with minimum attainable temperature.
7.Verify that the oven's plate rotation is speed is optimal and not too high to spill the food kept over it.
8.Verify that the oven's door gets closed properly.
9.Verify that the oven's door open's smoothly.
10.Verify the battery requirement of the microwave oven and check that it function's smoothly at that power.
11.Verify that the text written over the oven's body is clearly readable.
12.Verify that the digital display is clearly visible and functions correctly.
13.Verify that the temperature regulator is smooth to operate.
14.Verify that the temperature regulator works correctly.
15.Check the maximum capacity of oven and test its functioning with that volume of food.
16.Check oven's functionality with different kinds of food - solid, liquid.
17.Check oven's functionality with different food at different temperature.
18.Verify oven's functionality with different kinds of container material.
19.Verify that the power cord of oven is long enough.
20.Verify that the usage instruction or user manuals have clear instructions
------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Notepad

1.Verify that on launching the notepad application, the notepad editor should open with its default size.
2.Verify that user can write/type alphabets from a standard keyboard.
3.Verify that user can type numeric from a standard keyboard
4.Verify that user can type special characters and symbols on notepad editor window.
5.Verify that by default the font size is normal or as per the specifications.
6.Verify that user can set the font size and family.
7.Verify that user can save the text in a file.
8.Verify that user can open any exiting file in notepad.
9.Verify that file formats not permitted by notepad are not loaded and doesn't corrupt the application.
10.Verify that user can append text to any file and again save the file.
11.Verify that user can select, copy and paste text.
12.Verify that user can select, cut and paste text.
13.Verify that user can select and delete a text.
14.Verify that user can delete a text using backspace and delete buttons.
15.Verify that user can navigate through the text in file using the arrow keys.
16.Verify that user can navigate through the text in file using mouse pointer.
17.Verify that user can edit and delete data in between the text file.
18.Verify that user can undo any latest change done in file.
19.Verify that user can redo any change undone by undo option.
20.Verify that user can search for single or multiple characters and words through the file.
21.Verify that user can search and replace single or multiple characters and words through the file.
22.Verify that user can resize the notepad window.
23.Verify that user can minimize the notepad editor window.
24.Verify that user can maximize the notepad editor window.
25.Verify that user can close the editor window by clicking the cross icon.
------------------------------------------------------------------------------------------------------------------------------

Test Scenarios of Online Examination System

Test Scenarios for Setting Exam Functionality

1.Verify that the application has portal to add subject wise questions and their options.
2.Verify that the examiner can set the examination details like 'Exam Name', 'Subject', and ‘Exam Code' etc.
3.Verify that the examiner can set the total number of questions and based on the number of questions, the examiner is presented with the window to add question details.
4.Verify that examiner can set details for each question - Question, Options, and Marks etc.
5.Verify that examiner can set or leave the option of negative marking.
6.Verify that the examiner can set the passing marks for clearing the exam.
7.Verify that examiner can set time duration for the whole exam or for individual questions if required.

Test scenarios for Student's section

1.Verify the student can choose the examination based on the exam name or code.
2.Verify that the student should see the options to fill the required details like name, roll number etc. before starting the exam.
3.Verify that after filling the required details user should see the option to begin the exam along with instructions.
4.Verify that once the examination begins a timer gets started based on the test duration.
5.Verify that for each question user is presented with option for multiple choice questions (MCQ) type questions.
6.Verify that user can chose single (radio button) or multiple (checkbox) option based on the type of questions.
7.Verify that on question's window user is presented with options to move to previous or next question.
8.Verify that once all the questions are answered or passed user can end the test.
9.Verify that if the time duration for the test gets reached the test automatically ends.
10.Verify that once the test is submitted, the test evaluation is performed considering the positive and negative marking.
11.Verify that on evaluation user is presented with Pass/Fail status along with Marks secured, questions attempted etc.
------------------------------------------------------------------------------------------------------------------------------

No comments:

Post a Comment