Skip to content

Expose aggregated test execution metrics including retries #7393

@DanielGilOrtiz

Description

@DanielGilOrtiz

Summary

Expose aggregated test execution metrics that include all retry attempts, instead of reporting only the outcome of the last attempt.

Background and Motivation

When Microsoft Testing Platform runs tests with retries, each attempt produces its own TRX file. Azure DevOps can merge these files and visually show all attempts, but this aggregated information is not available programmatically.
This makes it impossible to build custom automation or quality gates based on actual execution behavior.

Proposed Feature

Expose aggregated execution metrics directly in the final TRX file generated by Microsoft Testing Platform, so that it contains information not only about the last execution attempt but about all attempts, including retries.

These aggregated metrics could include:

  • total executions including retries
  • failures across all attempts
  • number of retry attempts per test
  • tests that only passed after retry

This approach avoids introducing new report types or additional files, and keeps the information accessible through the existing TRX pipeline that tools already consume.

Alternative Designs

Manually parsing all TRX files is possible but unreliable and not automation‑friendly. A built‑in solution would be more robust and portable.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions