3. Test Scenarios & Test Cases with Excel Sheet Format (1).pdf

Software Testing Tools-Ch.3 Test Scenarios & Test Cases with Ms-Excel

1. Test Scenario/ Test Case design-









PO PO Tester Tester

SRS/FRS/CRS-
 SRS/ FRS derived from BRS
 SRS/ FRS prepared by PO
 SRS defines functional requirement to development & System requirement that will be
used.
 SRS/ FRS will contains
1. Functional requirement
2. Functional flow diagram
3. Use Cases
4. Screenshot
 SRS will contains multiple User Case

SRS/ FRS/ CRS
User Cases/ US
Test scenario
Test Cases
Design

2. Use Case/ User Story-
 Use cases/User story derived from SRS/ FRS
 Use cases/User story prepared by PO
 Use cases/User story defines Functional / Single specific requirement
 Use cases/User story will contains
1. Description – Details about the requirement
2. Acceptance Criteria – Does & Don’t about requirement
Test scenario VS Test cases
Test scenario-
 Test Scenario defines ways to test functionality of an application/ build
 Test scenario will be prepared by tester
 Test Scenario derived from Use cases/User story
 Test Scenario will defines “What to test”
 Test Scenario will contains / includes multiples test cases
 Test Scenario always defines “high level test cases”
 Test Scenario always written in +ve ways
 Ex. Login Page- Username text box, Password, Submit button
 US- Login Page 
Description Criteria-.
Username text box should accept only mobile & email id. Password test box will contains
4 to 6 charter combination.
Acceptance Criteria –
Login page should accept mobile no as a username & password will contains 4 to 6
charter combination.




Username

Password


Submit

3.  Test Scenario of login page-
1. Verify login page by passing mobile no. in username test box
2. Verify login page by passing email ID in username test box
3. Verify login page by passing data in Username & Password text box

Test cases-
 Test cases defines steps to test functionality of an application/ build
 Test cases will be prepared by tester
 Test cases derived from Test Scenario
 Test cases will defines “How to test”
 Test cases will contain / includes input values, Output values & result
 Test cases will contains Test steps, Expected result, Actual result, Pass/Fail criteria
 Test cases always defines “Low level test cases”
 Test cases always written in +ve ways & -ve ways


 Ex. Test Scenario of login page -Verify login page by passing mobile no. in username
test box
 Test cases-
1. Verify login page by passing Idea mobile no. in username test box
2. Verify login page by passing Vodafone mobile no. in username test box
3. Verify login page by passing Airtel mobile no. in username test box
4. Verify login page by passing BSNL mobile no. in username test box
5. Verify login page by passing JIO mobile no. in username test box
6. Verify login page by passing invalid mobile no. in username test box
7. Verify login page by passing blank/ null values in mobile no. into username test box

4.  Ex. Test Scenario of login page - Verify login page by passing email ID in username
test box
 Test cases-
1. Verify login page by passing @gmail.com id’s in username test box
2. Verify login page by passing @redefmail.com id’s in username test box
3. Verify login page by passing @yahoo.com id’s in username test box
4. Verify login page by passing @hotmail.com id’s in username test box
5. Verify login page by passing @outllook.com id’s in username test box
6. Verify login page by passing @doamin.com id’s in username test box
7. Verify login page by passing invalid @gmail.com id’s in username test box
8. Verify login page by passing invalid @redefmail.com id’s in username test box
9. Verify login page by passing Null/ blank values in username test box

 Ex. Test Scenario of login page - Verify login page by passing data in Username &
Password text box
 Test cases-
1. Verify login page by passing valid data in Username & valid data in Password text
box
2. Verify login page by passing Invalid data in Username & valid data in Password text
box
3. Verify login page by passing valid data in Username & Invalid data in Password text
box
4. Verify login page by passing Invalid data in Username & Invalid data in Password
text box
5. Verify login page by passing Null/ Blank data in Username & valid data in Password
text box
6. Verify login page by passing valid data in Username & Null/ Blank data in Password
text box
7. Verify login page by passing Null/ Blank data in Username & Invalid data in
Password text box

5. 8. Verify login page by passing Null/ Blank data in Username & Null/ Blank data in
Password text box
9. Verify login page by passing Null/ Blank data in Username & Null/ Blank data in
Password text box
10. Verify after mouse over in submit button

 Ex. US – Login Page – Flipkard login page



Test scenario-
1. Verify the login page by passing mobile number
2. Verify the login page by passing email
3. Verify the login page by password
4. Verify the login button functionality in Flipkard login page

Test scenario- Verify the login page by passing mobile number
Test cases –
1. Verify the login page by passing BSNL mobile number
2. Verify the login page by passing VI mobile number
3. Verify the login page by passing Airtel mobile number

6. 4. Verify the login page by passing JIO mobile number
5. Verify the login page by passing MTNL mobile number
6. Verify the login page by passing invalid BSNL mobile number
7. Verify the login page by passing invalid VI mobile number
8. Verify the login page by passing invalid Airtel mobile number
9. Verify the login page by passing invalid JIO mobile number
10. Verify the login page by passing invalid MTNL mobile number
11. Verify the login page by passing null/ Blank mobile number


Test scenario -Verify the login page by passing email
Test cases –
1. Verify the login page by passing email id (@gmail.com)
2. Verify the login page by passing email id (@yahoo.com)
3. Verify the login page by passing email id (@readiffmail.com)
4. Verify the login page by passing email id (@hotmail.com)
5. Verify the login page by passing email id (@outllok.com)
6. Verify the login page by passing email id (@domain.com)
7. Verify the login page by passing invalid email id ([email protected])
8. Verify the login page by passing invalid email id
9. Verify the login page by passing null/ Blank email id

Test scenario - Verify the login page by password
Test scenario - Verify the login button functionality in Flipkard login page

7. Q. Write test cases of following objects?
 Login-Page


Description Acceptance criteria
Login page of VCTC application contains
Login text box, password text box & sign in
button. This login page will provided for
VCTC student & staff login, from which they
login into their VCTC account page. Login
page will contains all page as per standard
colour as suggested.
Login text box accept only mobile no. Existing
in your domain
Login text box will unmasked
Login text box doesn’t accept other then
VCTC mobile number
Password text box will accept One Capital
letter, One special char, One number
Password text box will masked
Password text box doesn’t accept One special
char, One number these combination
Password text box doesn’t accept One Capital
letter, One number these combination
Password text box doesn’t accept One Capital
letter , One Capital letter combination

8. 1. UI Test Scenarios for Login Page -
 Verify that the entire web element including text-boxes, buttons, and links are
present on the Login page.
 Verify that the size, colour, and UI of the different elements are as per the
specifications.
 Verify that the web application as per standard dimensional
 Verify that the application’s UI is responsive i.e. it should adjust to different
screen resolutions and devices.

2. Functional Test Scenarios for Login Page
 Verify that the user is able to navigate or access the different controls by pressing
the ‘Tab’ key on the keyboard.
 Verify that the password is in masked form when entered.
 Verify if the password can be copy-pasted or not.
 Verify for entering a valid User Name, valid Password & pressing sign in button
 Verify for entering a valid User Name and invalid Password & pressing sign in
button
 Verify for entering a invalid User Name and valid Password & pressing sign in
button
 Verify for entering a invalid User Name and invalid Password & pressing sign in
button
 Verify that only for entering User Name & pressing sign in button
 Verify that only for entering Password & pressing sign in button
 Verify that only for pressing sign in button
 Verify that entering exceed charter in User Name and Password text box (BVA &
ECP)
 Verify if there is a checkbox with the label “remember password” on the login
page.
 Verify that for a valid mobile no in user name box & for valid password &
pressing sing in button.

9.  Verify that for a invalid mobile no in user name box & for valid password &
pressing sing in button.
 Verify that for a valid email id in user name box & for valid password & pressing
sing in button.
 Verify that for a valid student mobile no (start with 9, 8, 7) in user name box &
for valid password & pressing sing in button.
 Verify that for a valid staff mobile no (start with 9, 8, 7) in user name box & for
valid password & pressing sing in button.
 Verify that for a valid mobile no in user name box & for valid password which
contain one spec char, one Capital letter, one No. & pressing sing in button.
 Verify that for a valid mobile no in user name box & for invalid password which
contain one Capital letter, one No. & pressing sing in button.
 Verify that for a valid mobile no in user name box & for valid password which
contain one spec char, one No. & pressing sing in button.
 Verify that for a valid mobile no in user name box & for valid password which
contain one spec char, One Capital letter & pressing sing in button.
 Verify that for a valid mobile no in user name box & for valid password which
contain (change sequence) one spec char, One Capital letter, one No. & pressing
sing in button.

 Google search
1. UI Test Cases for Google Search
 Verify that Google Logo is present and centre aligned
 Verify that the search textbox is centre aligned and editable
 Verify that in the search result- webpage’s title, URL and description are present
 Verify that clicking the search result will lead to the corresponding web page
 Verify that user can navigate to a page number directly or move to previous or
next page using the links present
 Verify that different languages links are present and gets applied on clicking the
same

10.  Verify that the total number of results for the keyword is displayed
 Verify that the time taken to fetch the result is displayed

2. Functional Test Scenarios for Login Page
 Verify that the response fetched for a particular keyword is correct and related to
the keyword, containing links to the particular webpage
 Verify that the response are sorted by relevancy in descending order i.e. most
relevant result for the keyword are displayed on top
 Verify that response for multi word keyword is correct
 Verify auto-suggestion in Google e.g. providing input as ‘fac’ should give
suggestions like ‘facebook’, ‘facebook massenger’, ‘facebook chat’ etc
 Verify that response fetched on selecting the suggested keyword and on providing
the keyword directly should be same
 Verify that the suggestion provided by Google are sorted by most popular/relevant
suggestions
 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
 Verify that misspelled keyword should get corrected and response corresponding
to the correct keyword should get displayed
 Verify that multi word misspelled keywords also get corrected
 Verify that total number of results fetched for a keyword
 Verify that the search response should be localised that is response should be
more relevant to the country/area from which the search request is initiated
 Verify Google calculator service- make any arithmetic request, calculator should
get displayed with correct result
 Verify search response for a large but valid strings
 Verify that incorrect keywords – keywords not having related result should lead to
“did not match any documents” response
 Verify that user can make search using different languages

11.  Verify that for a keywords, some related search terms are also displayed to aid
user’s search
 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
 Verify Google’s advanced search options like- searching within a website,
searching for files of specific extension
 Verify if the search is case-insensitive or not
 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)

Q. writes test cases of following thing
1. Pen, Table, Chair, Mobile phone, Fan, Watch, Keyboard, Paper
2. Gmail login page, Paytm login page, Face-book sign up page, IRCTC sign up page,
whatup application
3. Flipkard home page, Amazone home page, Flipkard Mobile buy page, Make my trip
travel page from Pune to Mumbai.

Refer side for more test cases - https://artoftesting.com/test-case
Difference between Test scenarios & Test Cases?

Sr.No Test Scenario Test Case
1 Test Scenario are derived from the user
stories
derived from the Test Scenario Test Case are
2 Test Scenario focuses on “What to test” Test Case focuses on “How to test”
3 Test Scenario high level actions Test Case low level actions
4 Test Scenario describes test
condition/requirements/functionality,
which we have to validate
Test Case describes validation procedures of
each functionality or requirements

12. Test cases format – Excel sheet fields
 In my project, we are writing text cases in excel sheet
 These are field which in present in excel sheet,

1. Test case Id
2. Priority
3. Reference,
4. Test scenario,
5. Pre-request condition,
6. Test cases,
7. Test step,
8. Excepted result,
9. Actual result,
10. Status- Pass/ Fail criteria
11. Comments
Or
1. Test scenario ID
2. Test scenario description
3. Test case ID
4. Test case description
5. Test step
6. Pre-condition
7. Test data
8. Post condition
9. Expected result
10. Actual result
11. Status
12. Executed by
13. Executed date
14. Comments