Improve Test Report Generation to Handle Duplicate Suite Names #729
Description
Is your improvement proposal related to a problem? Please describe.
The current behavior of the test report generation tool when processing multiple reports that contain identical test suite names is to display only one of the suites, resulting in an incomplete overall report.
This scenario commonly occurs when running the same set of tests across different environments, configurations (e.g., various kernel or OS permutations), or concurrent jobs, and the automatic mechanism for differentiating suite names is not utilized.
Describe the solution you'd like
Desired Behavior:
- Prevent Loss of Data: When test report files contain duplicate suite names, the tool should not discard the data from the duplicate suites. Instead, it should include all of them in the final report.
- Ensure Uniqueness: The tool should automatically apply a unique identifier (such as an incremental suffix like
(1),(2), etc.) to the conflicting suite names in the report to distinguish them. - Potential Enhancement: Consider using metadata available in the report file, such as the associated job or block name, to automatically generate a unique, descriptive label for the suite in case of a clash.
Describe alternatives you've considered
TBD
Additional context
No response