Execution Status Mapping Reference
This reference describes the status mapping fields used to determine the execution status of imported test case and test step runs. Configure these mappings in a Custom Automation Template to associate XML elements or values with the corresponding QMetry execution statuses.
Note
tatus mapping applies only to execution results. It does not affect test case creation or versioning.
Test Case and Test Step Run Status Fields
Use the following mapping expressions to determine the execution status of imported test case and test step runs.
QMetry Status | Description | Expression |
|---|---|---|
Passed | Identifies successful executions. | ${suite.test.class.testmethod.status} ${suite.test.class.testmethod:status} |
Failed | Identifies failed executions. | ${testsuites.testsuite.testcase.failure} ${testsuites.testsuite.testcase.step.failure} |
Aborted/Error | Identifies aborted or errored executions. | ${testsuites.testsuite.testcase.error} ${testsuites.testsuite.testcase.step.error} |
Skipped | Identifies skipped executions. | ${testsuites.testsuite.testcase.skipped} ${testsuites.testsuite.testcase.step.skipped} |
Default Status
The Default Status determines the execution status when none of the configured status mappings match the imported XML.
Note
Default Status applies only to test case runs.
Configuration | Result |
|---|---|
True | Marks the execution as Passed. |
False | Marks the execution as Failed. |
When an exact status mapping is unavailable, QMetry applies the following fallback rules.
Fallback Status Behaviour
When an imported XML does not contain a configured status mapping, QMetry applies the following fallback behavior.When an imported XML does not contain a configured status mapping, QMetry applies the following fallback behavior.
XML Element | Default Behavior |
|---|---|
<failure> | Marks the execution as Failed. |
<error> | Marks the execution as Failed, unless a custom Aborted execution status exists. |
<skipped> | Marks the execution as Not Applicable, unless a custom Skipped execution status exists. |
Framework-Specific Considerations
Some automation frameworks, such as JUnit, do not explicitly record successful executions. For these frameworks, configure Default Status to True so that executions without <failure>, <error> or <skipped> elements are treated as Passed.