I built a .NET test reporter to solve two problems I kept seeing in test automation

Description and use

Ace Reports automatically captures API traffic, retry attempts, and screenshots, flags flaky tests, and produces a self‑contained HTML report, eliminating the need for manual reporting code.

Problem

Test reports in .NET automation often indicate a failure but lack details on what caused it, making debugging hard.

Outcome

Ace Reports provides automated, detailed test reporting that surfaces flaky tests and captures rich execution data, eliminating the need for manual reporting code and enabling faster debugging.

Workflow

• Write tests normally using xUnit, NUnit, MSTest, or Reqnroll.
• Run tests with Ace Reports enabled.
• Ace Reports intercepts test execution, automatically records API traffic, retry attempts, and screenshots on failure.
• After execution, Ace Reports generates an HTML report that includes flaky‑test detection and full history.
• Review the report to investigate failures.
• Iterate tests based on insights.
• Repeat.

Evidence

I built Ace Reports — a .NET test reporter with automatic API capture and flaky-test detection

Source

If a test fails and then passes on a retry, I don't want the report to simply show the final Passed result. I want to know that the test was flaky, how many attempts it took, and what happened during those attempts.

Source

I don't want testers to have to modify their test scripts just to populate the report. Things like API requests/responses, retry information, execution details, and screenshots on failure should be captured automatically wherever possible.

Source

Ace Reports generates a self-contained HTML report, with no reporting server required. It currently has adapters for xUnit, NUnit, MSTest, and Reqnroll.

Source