Scribd
Upload
96 views5 pages

How To Write Test Scenarios

The document outlines five steps to create test scenarios: 1) read requirement documents, 2) determine possible user actions and objectives, 3) list test scenarios for each software feature, 4) create a traceability matrix matching requirements to test scenarios, and 5) have scenarios reviewed. It provides tips - that each scenario should verify a minimum of one requirement in isolation before combining, and to only run selected scenarios based on priorities. An example test scenario for login in an e-commerce application is given.

Uploaded by

Adem Ozturk
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
96 views5 pages

How To Write Test Scenarios

The document outlines five steps to create test scenarios: 1) read requirement documents, 2) determine possible user actions and objectives, 3) list test scenarios for each software feature, 4) create a traceability matrix matching requirements to test scenarios, and 5) have scenarios reviewed. It provides tips - that each scenario should verify a minimum of one requirement in isolation before combining, and to only run selected scenarios based on priorities. An example test scenario for login in an e-commerce application is given.

Uploaded by

Adem Ozturk
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

How to Write Test Scenarios

As a tester, you can follow these five steps to create Test Scenarios-

Step 1: Read the Requirement Documents like BRS, SRS, FRS, of the System Under Test (SUT).
You could also refer uses cases, books, manuals, etc. of the application to be tested.

Step 2: For each requirement, figure out possible users actions and objectives. Determine the
technical aspects of the requirement. Ascertain possible scenarios of system abuse and
evaluate users with hacker's mindset.

Step 3: After reading the Requirements Document and doing your due Analysis, list out
different test scenarios that verify each feature of the software.

Step 4: Once you have listed all possible Test Scenarios, a Traceability Matrix is created to verify
that each & every requirement has a corresponding Test Scenario

Step 5: The scenarios created are reviewed by your supervisor. Later, they are also reviewed by
other Stakeholders in the project.

Tips to Create Test Scenarios


Each Test Scenario should be tied to a minimum of one Requirement or User Story as per the
Project Methodology.
Before creating a Test Scenario that verifies multiple Requirements at once, ensure you have a
Test Scenario that checks that requirement in isolation.
Avoid creating overly complicated Test Scenarios spanning multiple Requirements.
The number of scenarios may be large, and it is expensive to run them all. Based on customer
priorities only run selected Test Scenarios
Example 1: Test Scenario for eCommerce Application
Test Scenario 1: Check the Login Functionality
Test cases:
Check system behavior when valid email id and password is entered.
Check system behavior when invalid email id and valid password is entered.
Check system behavior when valid email id and invalid password is entered.
Check system behavior when invalid email id and invalid password is entered.
Check system behavior when email id and password are left blank and Sign in entered.
Check Forgot your password is working as expected
Check system behavior when valid/invalid phone number and password is entered.
Check system behavior when "Keep me signed" is checked
Youtube link on example :
https://www.youtube.com/watch?v=BBmA5Qp6Ghk
https://youtu.be/pl7xEDJ6OO8
https://www.youtube.com/watch?v=g0PrXoWKM2Y

You might also like