Automation Hierarchy Settings for TestNG and JUnit Frameworks
There are two ways users can define the hierarchy within the Test Cycle - Test Case - Test Step when handling Automation Files uploaded to QTM4J for both TestNG and JUnit: (A) pass parameters while uploading the result files or (B) configure settings in QTM4J.
You can set the default Automation Hierarchy from Automation > Automation API > Settings. When the hierarchy is not provided by the user explicitly, it is referred from Automation > Automation API > Settings > Test Cycle - Test Case - Test Step Hierarchy configuration for both TestNG and Junit Frameworks. You can configure the Automation Hierarchy to define the Test Cycle - Test Case - Test Step Hierarchy while importing the automation results into QTM4J. The test cycle, test case, and test steps will be identified accordingly in the test result files and will be imported into QTM4J.
The default hierarchy will be “1” for both frameworks.
→ Required Permissions: Only project admins can configure the hierarchy settings.
How to access the Settings?
1. Open the QMetry menu and select Automation.
The Test Cycle name will be auto-generated or manually provided by the user and the Test Case Name is created as Test Case. If there are multiple suites in the result file then only a single cycle will be created.
Append Test Suite Name to Test Case Name while creating the Test Case Summary such as "Test Suite: Test Case Name": Select this option to make it easier to identify which test case belongs to which test suite. It applies to Hierarchy 2 and 3.
Note: If the Test Name or Test Suite Name length is more than 255 characters, the name will be truncated.