Identifying How to Create Test Scenario And Perform Scenario Testing
Posted By : Monika Garg | 27-Feb-2018
What is a Test Scenario?
Test Scenario consists of two words (Test + Scenario). Where Test means to verify the functionality of the application and Scenario means any user peregrination. When combined it says validate the user peregrination. It is also known as Test Condition or Test Possibility means any functionality that can be tested.
Test scenario is just a story which explains the usage of the software by an end user.As a tester, you may put yourself in the end user’s shoes and figure out the real-world scenarios and use cases of the Application Under Test.A test scenario can be an independent test case or a series of test cases that follow each other.
Most of the people gets confused with the Test Scenario & Test Case. Test Scenario - what is to be tested and a Test Case - how is to be tested. Please have a look at the difference between Test Scenario and Test Case.
Example
Test Scenario: Validate the Login Page
- Test Case 1: Enter a valid username
- Test Case 2: Enter a valid password
- Test Case 3: Enter invalid credentials
What is Scenario Testing?
The exhaustive testing is impossible due to all combination of input values and a large number of possible paths in the software.Scenario testing is done to make sure that the end to end functionality of software application under test is working as expected and ensures that all business flows are working as expected. As Scenarios are nothing but the User Journeys. Scenario testing helps in finding a lot of defects which cannot be found with other types of testing.
Important points while writing Test Scenario:
- Creating Test Scenarios ensures complete Test Coverage.
- Domain knowledge is very important to get the deeper knowledge of the software application.
- Test Scenarios should be reviewed by various stakeholders like Project Manager/Business Analyst or anyone else who understands the requirements very well.
- While creating the test scenario, we must be covered the negative and out-of-the-box testing
- Scenario mapping helps in avoiding any miss and ensures that each and every requirement is directly mapped to the number of scenarios
How to create a Test Scenario?
There are 7 steps to create Test Scenarios which is followed by the testers-
Step 1: Testers must have a good understanding of the Requirement Documents like BRS, SRS, FRS, of the Application Under Test (AUT).
Step 2: Understand the project workflow, and wireframes (if available) and relate the same to the requirement.
Step 4: For each requirement, figure out possible users actions and determine the technical phase of the requirement. Make possible scenarios of the software system evaluate users with hacker's mindset.
Step 5: After reading the Requirements Document and Analysis it, Create the list of test scenario to verify each feature and functionality of the software
Step 6: A Traceability Matrix created to verify that each & every feature and requirement has a corresponding Test Scenario.
Step 7: The scenarios created are reviewed by your supervisor and also reviewed by other Stakeholders in the project.
Cookies are important to the proper functioning of a site. To improve your experience, we use cookies to remember log-in details and provide secure log-in, collect statistics to optimize site functionality, and deliver content tailored to your interests. Click Agree and Proceed to accept cookies and go directly to the site or click on View Cookie Settings to see detailed descriptions of the types of cookies and choose whether to accept certain cookies while on the site.
About Author
Monika Garg
Monika is a bright QA Engineer with skills in manual testing and always eager to learn new things. Her hobbies are listening to music and playing games.