...
When a Drill Down Test Case is added to the Test Plan a new backend Test Run is automatically created and a Run ID is generated. The description holds the technical name of the Test Plan and the Test Case. All Drill Down Variants selected during the creation of Drill Down Test Case are automatically added into Drill Down Variant selection for the generated Test Run.
To execute a Drill Down Test Case from Test Management click on 'Execute'. Afterward, the standard Drill Down Testing scenario is displayed. Please refer to 8.3.1 ('Test Scenario EQS_DRILL (Drill Down testing)') section for a more detailed description of each scenario step.
...
You can select which of the Drill Down Variants are to be used or create new Drill Down Variants to be added to the Test. When the Test Run is generated through the Validate Test management the variants are already preselected for the Drill Down Test Case.
Once the variants are selected for the Test Run, you can save the selection by clicking on the 'Save' button (Ctrl + s).
In the following ways it is possible to add Drill Down Variants to the list:
Create New Drill Down Variant - (SHIFT + F1). For detailed information about the creation of the Drill Down variant please refer to 7.4.1 ('Create new Drill Down Variant') section,
Add Existing Drill Down Variant - (SHIFT + F4) displays all of the existing Drill Down Variants in the system, and you can select one or more variants to be added into the current Test Run.
Add Drill Down Variants of Run - (SHIFT + F5) you can select the Variants used in another (distinct from current) run and add them into current the run as well.
Generate Drill Down Variants - (SHIFT + F6) please refer to 7.4.2 to ('Generate Drill Down Variants') section for more information.
Copy Variants - Please refer to 7.1.14 7.4.7 ("('Copy DrillDown Variants"') section for function details.
...
In the third scenario, some or all data returned by InfoProviders are not the same. In this case, a new test cycle begins, and the erroneous data is checked. Using the Validate setting 'DrillDown maximum records', for the first added characteristic (the one added at the start of the first cycle) the X number of distinct values that belong to erroneous records are selected. These values act as a filter value for this characteristic in the next test cycle (drill down into erroneous records).
The next characteristic in is the order of specified Drill Down characteristics (if no more are available then the execution stops here) is added to ListCube for reading and then another characteristic is selected for the output. The ListCube reads are repeated for both InfoProviders with the new settings and the data is then compared again. Afterward either a new test cycle begins using the same logic just described, or execution ends here, depending on the result of the comparison.
If Validate setting 'DrillDown additional aggr.' is set to 'X' in each cycle when InfoProviders are read the returned data is aggregated again. This functionality can be used for cases when ListCube returns multiple rows with the same key because of unsupported functions.
...