Test Scenarios [+ quick intro to test formality]
How to create a Test Scenario?
1) Read the requirements 2) For each requirement, figure out possible user actions and objects, both good/bad 3) List out different test scenarios that verify each feature of the software 4) Create a Traceability Matrix to verify that each requirement has a Test Scenario 5) Scenarios are reviewed by supervisor, then stakeholders
When not to create Test Scenarios?
- AUT is complicated, unstable, project time crunch - Projects that follow Agile methods - Maintenance, since scenarios are most likely already documented from previous use
Tips on Creating Test Scenarios
- each test scenario should be tied to a requirement - prior to creating a test scenario that covers multiple requirements, each requirement should have a unique test scenario - avoid overly complicated scenarios spanning multiple requirements - number of scenarios can be large, but running them all is expensive, choose based on customer priorities
Why create Test Scenarios?
- ensure complete Test Coverage - stakeholders can approve to ensure primary functions are tested - quick tool to check testing efforts, therefore providing a way to create testing proposals for clients - help determine the most important end-o-end transactions and uses
What is Test Formality?
100% ad-hoc testing does not equate to actual testing. Testing is a very formal activity and documented in detail.
What is Scenario Testing?
A variant of software testing where scenarios are used. Often useful for larger/complex systems.
What is a Test Scenario?
Any functionality that can be tested; also known as a test condition or test possibility.