Execute Test Case User Action Documentation
Last updated
Last updated
The 'Execute Test Case' user action allows users to invoke entire test scripts as test steps within another script, promoting reusability.
Note:
Users can employ multiple 'Execute Test Case' actions within a single test script.
However, the invoked test script should not contain any 'Execute Test Case' actions, as this is not allowed.
To use the 'Execute Test Case' useraction:
Select 'Execute Test Case' under “Functions”.
Click the “Select Script” button to display modules within the project.
Choose a module and select the script for invocation.
The 'Execute Test Case' user action includes a parameterization feature, enabling users to test various scenarios. Test data is managed using a dedicated table called the Test Data Management (TDM) table, serving as the data source for parameterized test steps.
Required:
Script Name: Select the script to be invoked.
Optional:
Data: This field is used to select a row of the child script. It is used to run the parameterized scripts of the invoked script or use an asterisk (*) to select all rows.
If this user action is parameterized, the 'Data' field will be changed into 'Data Column', which is a mandatory field.
*Data Column: Specify the column name for the parent script.
We have implemented validation checks for the parameterized data table to ensure data integrity and accuracy.
1
false
false
Normal Execution
2
false
true
In the parent script, provide the row name of the 'parameterized child script' data table in the data field. Use an asterisk (*) to execute all rows.
3
true
true
In the parent script data table, specify the row name of the child script. An asterisk (*) can also be used to execute all rows.
4
true
false
This configuration performs a normal execution.
When 'Test 1' has parameterized steps with two rows of data, you can employ 'Test 1' in 'Test 2.' In the 'Data Column' field, indicate the test case serial name (e.g., Tc_1) for the test data execution.
When 'Test 1' contains parameterized steps with two rows of data, you can use 'Test 1' in 'Test 2.' Within the 'Data Column' field, you may specify (*) as a wildcard. In this scenario, both data and execution will be considered, resulting in two iterations before proceeding to the next step.
Preventing Invalid Row Names: Users cannot enter row names not present in the child script.
Enforcing Environment Consistency: The parent and child scripts must reside in the same environment for execution.
Requiring Complete Data Entry: Users must provide data for all cells in the parameterized data table.
Prohibiting Special Characters: Special characters such as commas(,) or pipe symbols (||) are not allowed in row names to prevent data discrepancies (e.g., Tc1, Tc2, or Tc1 || Tc2).
