Context:
In many organizations, there is a central repository of generic tests that are reused across multiple projects. To leverage these tests, project teams often copy them from the generic repository into their specific ETM project areas. Over time, the original tests in the generic repository may evolve (e.g., updated steps, new validations), but the copied versions in project-specific areas remain unchanged. This creates a risk of inconsistencies and outdated test coverage. The number of users impacted can be significant, as multiple projects rely on these shared test assets.
Problem:
Currently, when a test is copied from one project area to another, there is no easy way to track whether the copied version is still aligned with the latest version of the original test. Although the origin information and copy date are stored in the first line of the test history, users must manually check and compare dates, which is time-consuming and error-prone.
Example use case :
- A generic test is updated in the central repository after a bug fix.
- A project team continues to execute the outdated copied version without realizing the update exists.
- This leads to missed validations and potential non-compliance with quality standards.
Impact:
If this issue is not addressed:
- Projects may execute outdated tests, leading to gaps in validation and reduced product quality.
- Increased risk of non-compliance with standards or customer requirements.
- Additional support requests and manual checks, wasting time and resources.
- Loss of trust in the consistency and reliability of shared test assets.
Goal of the idea:
Provide a mechanism to automatically identify copied tests that are outdated compared to their original version in the generic repository.
Why it is useful ? :
-
Improved user experience: Users can quickly identify which tests need to be updated.
-
Data integrity and reliability: Ensures alignment between generic and copied tests.
-
Reduced support effort: Eliminates manual checks and reduces errors.
-
Compliance: Helps maintain consistency across projects and meet quality standards.
How should it work ? :
We propose two possible solutions :
- Minimum solution :
· Implement a report or dashboard in ETM that compares:
o The last modification date of the original test in the generic repository.
o The copy date recorded in the copied test’s history.
· If the original test was modified after the copy date, highlight the copied test in the report (e.g., with a color indicator or flag).
· Optionally, allow filtering by project area or test category for better usability.
· This feature should be generic and applicable to any scenario where tests are copied between project areas.
- Enhanced solution:
· When copying a test from one project area to another, automatically create a traceability link between the original test and the copied test.
· This link should have a validity status set to Valid by default.
· If the original test is modified after the copy, the link status changes to Suspect.
· The user can then review the differences and update the copied test if necessary, and finally set the link back to Valid.
· This approach provides dynamic monitoring and better control over test alignment.
