With test scenarios, test cases can be grouped for a specific execution purpose and executed from within the scenario. An alternative terminology for test scenario could also be test plan or test set. The test cases inside the test scenario are not copied or moved, but only referenced, which means the current version of the test cases is always used when executing the scenario. You can therefore add the same test case to different test scenarios and the test case will have an individual execution status within each scenario. The execution list within the test case will still show all executions, whether they where executed from the within test scenarios or directly from within the test case itself.
The test scenarios thus offer the possibility to plan executions, specify information about the planned execution and easily evaluate the execution status of the test cases in the different execution contexts. This could be, for example, the execution for a specific release or software version, for a a test environment or test object, or for a specific test phase, such as regression, and can then also be executed repeatedly as often as required.
In addition, the test case execution order can be defined, execution dependencies can be set, value sets and automation agents can be specified or testers can be assigned in the context of the scenario.
In order to create a new test scenario, click on the New button in the Navigation window to create a new test scenario. A new tab will open where you can specify the new test scenario. The user interface consists of the following areas:
Ribbon Bar
Properties of the test scenario (can be configured by changing the project template)
