Automation Hierarchy Settings for TestNG and JUnit Frameworks
You can define the Test Cycle > Test Case > Test Step hierarchy for automation files uploaded to QMetry Test Management for Jira in two ways:
Option A: Pass parameters while uploading result files
Option B: Configure settings in QMetry Test Management for Jira
You can configure the default automation hierarchy in Automation > Automation API > Settings. If the hierarchy is not explicitly defined during file upload, the system uses the configuration set under Test Cycle > Test Case > Test Step Hierarchy in the same settings path.
This hierarchy setting applies to both TestNG and JUnit frameworks. When importing automation results into QMetry Test Management for Jira, the test cycle, test cases, and test steps are identified based on this configuration and imported accordingly.
The default hierarchy will be “1” for both frameworks.
Required Permissions: Only project admins can configure the hierarchy settings.
How to access the Settings?
Click the QMetry menu and select Automation.
Go to the Automation API section.
Select the Settings tab.
Overwrite Automation Executions
Allow users to modify the execution results for automated executions: This setting is enabled by default for all existing projects and new projects.
Required Permission: Only the Project Admin can manage the settings.
Settings | Description |
|---|---|
Enabled | Users with Test Cycle Execute permission will be able to manually modify the execution record for automation executions, including modifying Environment, Build, Assignee, A.T, Attachments, Comments, Actual Outcome, Execution Custom Fields, and Execution Result. It also allows the deletion of test execution runs from the execution screen. The ability to link defects to execution will still be allowed and managed through Test Cycle Manage Defects permissions. The permission impacts the test execution screen, Executions tab on the test case detail page, and theJira story page. |
Disabled | Users with Test Cycle Execute permission will not be able to manually modify the execution record for automation executions, including modifying Environment, Build, Assignee, A.T, Attachments, Comments, Actual Outcome, Execution Custom Fields, and Execution Result. It also prohibits the deletion of test execution runs from the execution screen. The ability to link defects to execution will still be allowed and managed through Test Cycle Manage Defects permissions. The permission impacts the test execution screen, Executions tab on the test case detail page, and theJira story page. |
Settings for TestNG Framework
Note
If the hierarchy of Test Cycle, Test Case, and Test Step is externally passed, QMetry Test Management for Jira will override the default settings on this screen with the externally provided input.
Automation Hierarchy | Description |
|---|---|
1 (Default) | The Test Name is created as Test Case, and Test Methods are created as Test Steps in QMetry Test Management for Jira. |
2 | The Test Name is created as a Test Cycle, and the Test Method Name is created as a Test Case. If there are multiple tests in the result file, then multiple test cycles will be created based on the test name. |
3 | The Suite Name is created as Test Cycle, and the Test Method Name is created as Test Cases. If there are multiple suites in the result file, then multiple test cycles will be created based on the suite name. |
Append Test Name to Test Method Name while creating a Test Case Summary based on the Test Method, such as "Test Name: Test Method Name": Select this option to make it easier to identify which test method belongs to which test case. 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.If the Test Name or Test Suite Name length is more than 255 characters, the name will be truncated.
Settings for JUnit Framework
Note
If the hierarchy of Test Cycle, Test Case, and Test Step is externally passed, QMetry Test Management for Jira will override the default settings on this screen with the externally provided input.
Automation Hierarchy | Description |
|---|---|
1 (Default) | The Test Suite Name/Class Name is created as a Test Case and the Test Case Names are created as Test Steps in QMetry Test Management for Jira. |
2 | The Test Suite Name is created as Test Cycle, and the Test Case Name is created as Test Case. If there are multiple test suites in the result file, then multiple test cycles will be created based on the suite name., |
3 | The Test Cycle name will be auto-generated or manually provided by the user, and the Test Case Name will be 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.