×
Menu
Search
 
   
   
   
 

Defining Test Cases in Test Scenarios

 
In this section you will learn how to define test cases in a test scenario. You find information regarding the following topics:
 
 

1. Add test cases to a test scenario

 
There are different ways to add test cases to a test scenario.
 

a) Via navigation bar

 
You can add test cases to a scenario via the navigation bar at the bottom of an open test scenario. By clicking test cases the content switches to a new view that allows to specify test cases to be executed in the given test scenario. In the ribbon bar you find an add button.
 
 
A dialogue opens where you see all test cases in the project. You can either search for a specific test case or use one of your predefined filters. When you select a test case you can choose whether to add it at the beginning or at the end of the test scenario. After adding all desired test cases you can save your scenario.
 
 
If a test case is parameterized, the default value set is entered by default. All other value sets can be added by clicking in the test cases section on Value set and choosing a value set from the drop down.
 
 
The order of the test cases can be defined by buttons up and down.
 
 

b) From clipboard

 
You can add test cases to a test scenario using your clipboard. To do so, create a new test scenario. Select a test case from the grid and copy it to the clipboard.
 
 
Now go back to the test scenario and select 'test cases' in the navigation bar. Click on the arrow below the 'Add' button and select 'Add copied test cases from clipboard' to insert the copied test cases.
 
 

c) Via context menu

 
Alternatively you can define a set of test cases in a test scenario by selecting a set of them in the navigation. Then, right-click the selected ones and choose Create new test scenario.
 
 

2. Define run dependencies

 
After your test cases are added to the test scenario you can define a run dependency for your test cases. This is for example helpful, if one test case needs to be passed before the next one can be executed. This means that if a single test case failed, none of the other test cases should be executed. To do so add values to Run Dependency column in the test cases view within a test scenario.
 
 
There are two types of run dependencies: Soft dependencies and hard dependencies. Soft dependencies neglect the previous test result, e.g. first test case needs to be executed, before second one can start (it does not matter if test case is failed). When using hard dependencies the results are considered, e.g. first test case needs to be passed, before second one can start. For a soft dependency, just enter the index number of the test case, which the other test case should be dependent from. For a hard one, you need to enter an exclamation mark after the index number.
 

3. Define agents

 
If your test cases in the test scenario are automated you can define an agent for the execution directly in the test scenario. If you do not define an agent here, the agent will be assigned in the execution automatically. aqua allows you to only select an agent which supports the technology the test case is automated with. To define agents, click on 'Test Cases'. Here you find a column 'Agent'. When you click in the cell where you want to define an agent, a drop down appears where you can select the agent. The agent defined in the scenario will be always considered first.