Test Scenario is a term quite often discussed in software circles and this article is meant for providing more details about Test Scenario.
What is Test Scenario?
Any functionality that can be tested is called as Test Scenario. In this process, which is also known as Test Possibility or Test Condition, a tester will approach the product from the perspective of a real user and figure out the real world scenarios.
What is Scenario Testing?
Scenario testing is nothing but a form of software testing where scenarios will be used for testing the application. Scenarios will be more helpful while testing complicated systems.
Why Create Test Scenarios?
Following are the reasons for creating test scenarios.
- Complete test coverage can be ensured by creating test scenarios.
- Most of the stakeholders such as business analysts, developers and customers will agree with test scenarios as it ensures that the application under test is tested thoroughly and as it enusres the proper functioning of most common functions.
- Test work effort can be estimated quickly and hence proposal can be made to the client and also for the work force.
- They play an important role in determining the important end to end transactions or the end use of the application.
- Test scenario is critical in studying the end to end functioning of the program.
When not to Create Test Scenarios?
In the following circumstances test scenario may not be created.
- When the application under test is complicated and unstable, creating test scenario is not advisable. Similarly, it is not advisable when there is a time crunch in the project.
- When the projects follow Agile testing methodologies such as Scrum and Kanban, test scenario may not be created.
- For a new bug fix or regression testing.
How to Create Test Scenarios?
There are five steps to create Test Scenario.
- Go through the requirement documents of the application under test such as BRS, FRS, and SRS. Uses cases and manual of the application can also be referred.
- Figure out possible user actions and objectives for each requirement. Determine the technical aspects of the application. Verify the possibilities of system or application abuse. Here the tester should evaluate the users with the mind of a hacker.
- After reading the requirements and analysis, prepare a list of different test scenarios that test each and every aspects of the software application.
- A traceability matrix should be created after the list has been prepared to verify whether every requirement has a corresponding test scenario.
- The test scenarios created will be reviewed by the supervisor and other stakeholders of the project.
Tips to Create Test Scenarios
- Each test scenario should be related to at least one requirement, which is called as user story as per technical terminology.
- If you are creating a test scenario which will verify multiple requirements concurrently, ensure that there is a test scenario which can verify each requirement individually.
- Better to create more complicated scenarios covering multiple requirements.
- There will be more number of test scenarios and the cost involved in running test scenarios may be more. It is better to run only the necessary scenarios as per the priorities of the user.