What are Test Scenarios

Software Test Scenarios are a set of user actions that are performed to verify that software does what it should and not what it shouldn’t.  These are usually at quite a high level of granularity and will not cover all the detailed test cases to prove every aspect of the software.  Test scenarios relate directly to the functionality described in the requirements or user stories.  Or at least they should.

Traceable Tests

All tests should trace back to the language and intent of the user story or software requirement that described the functionality from a user perspective.   They should cover the positive and negative tests.  In other words they should test that the software works as it shouldn’t and behaves well if misused.  When a requirement or user story has multiple functional steps, the testing of them becomes more complex.  There is an exponential need for additional negative tests to ensure that when the user does something unexpected, the correct behaviour is checked for.

Test Scenario - autogenerated by ScopeMaster, illustrated alternative flows

The test suggestions automatically generated by ScopeMaster and are 100% traceable back to the functionality described in the requirements.

Test Scenarios not Test Cases

Comprehensive functional testing needs to cover detailed attribute boundary testing.  Test scenarios do not usually cover this level of detail, instead they are the framework (foundation) on which detailed acceptance tests can be appended.

The scenarios and steps that ScopeMaster® generates can be downloaded and then imported into a test management system.  Alternatively they are also available from the REST API.

Test steps within each test scenario, covering both positive and negative outcomes

ScopeMaster® automatically generates the positive and negative test steps for each functional step within a user story.

All Features