Test Case Versioning and Reusability During Automation Import
When you import automation results, QMetry determines whether to:
Create a new test case.
Reuse an existing test case version
Create a new version of an existing test case
Note
QMetry compares the version only within the current project..
Import Processing Flow
QMetry follows the following process during the import: During automation import, QMetry performs the following steps:
Locate the Test Case.
Compare the imported test case with existing versions.
Determine whether to reuse an existing version or create a new version.
Handle missing referenced records.
Locate the test case
QMetry locates the test case based on the field mapped in the automation template.
Mapping Field | Lookup Behavior |
|---|---|
Test Case Summary | Searches for a test case whose summary exactly matches the imported summary. |
Test Case Entity Key | Searches for a test case using the specified entity key. |
Compare Test Case Versions
After locating the test case, QMetry compares the imported test case with all existing versions.
The comparison includes:
Test case summary
Test step descriptions
Test step sequence (order)
Note
Any change to the test step content or the order of test steps is treated as a functional change and results in the creation of a new version.
Versioning Decision
Based on the comparison, QMetry determines whether to reuse an existing version or create a new one.
Test Case Found | Summary Matches | Steps Match | Step Order Matches | Action |
|---|---|---|---|---|
No | - | - | - | Create a new test case |
Yes | Yes | Yes | Yes | Reuse the existing version. |
Yes | Yes | No | - | Create a new version. |
Yes | Yes | Yes | No | Create a new version. |
Yes | No | - | Steps Changed or Reordered | Create a new version. |
Note
QMetry compares both the content and the order of test steps. A change to either creates a new version.
Any modification to the test step content or the order of the test steps is treated as a functional change and results in the creation of a new version.
Handling Missing Referenced Records
If a referenced record cannot be found during import, QMetry handles it as follows:
Referenced Record | If record not found | Import Behaviour |
|---|---|---|
Test Case | Test case does not exist. | Creates a new test case and continues the import. |
Test Suite (Entity Key) | Test suite does not exist. | Stops the import and displays an error. |
Requirement (Entity key) | Requirement does not exist. | Imports the execution results without linking the requirement. |
Best Practices
Maintain a consistent test step order if you want imported execution results to reuse an existing test case version.
Expect a new version whenever test steps are added, removed, modified, or reordered.
Verify that referenced test suites exist before importing automation results to avoid import failures.
Missing requirements do not stop the import, but the requirement association is not created.