Test Case
To add an existing Test case to automated Test Run using automation API, the automation attributes come into picture. See the below-attached screenshot for more details about Automation Attributes. QMetry uses Automation Attributes to identify the test cases and test scenarios to be reused during the automation. The automation attributes work based on the automation framework and testassethierarchy used during automation.
There are 2 hierarchies, TestScenario-TestCase and TestCase-TestStep.
Automation Attributes should be defined in your existing Test case according to the type of hierarchy and automation framework you are using prior to import.
Below is the table that shows how automation attributes should be defined as per the automation framework result file and Test Case hierarchyand testassethierarchy used.
Note: The result file should be in QMetry Supported format.
Hierarchy 1: TestCase-Test-Step Hierarchy : Step
| Automation Framework | Test Case Attribute 1 | Test Case Attribute 2 |
|---|---|---|
| Cucumber | Scenario Id | Feature URI |
| TestNG | Test name | Class name |
| JUNIT | Class name | Testsuite name |
| QAS | metaData name | |
| HPUFT | Action Name |
Test Scenario
Users can add an existing Test Scenario to Automated Test Run using the Automation Attribute feature. Users have to map the Attributes in accordance with their respective Automation Framework. Refer the table below:
TestScenario-TestCase Hierarchy : Hierarchy 2 : TestScenario-TestCase
| Automation Framework | Test Scenario Attribute 1 | Test Scenario Attribute 2 | Test Case Attribute 1 | Test Case Attribute 2 |
|---|---|---|---|---|
| Cucumber | Scenario Id | Feature URI | Keyword | Name |
| TestNG | Test name | Class name | Method name | Class name |
| JUNIT | Class name | Testsuite name | Class name | Testcase name |
| QAS | metaData name | checkPoints message | ||
| HPUFT | Action Name | Step name | Action name |
For any further questions contact QMetry Support.