AceReportsWebsite: Every test execution evidence in one HTML report.

When a test fails in CI, the default report shows the assertion and the stack trace. It doesn’t show what the API returned, what was on screen, or whether the test only failed on a retry.

So I built Ace Reports. It writes one self-contained HTML file per run with all of that captured automatically.

What you get, without changing your tests:

Every API call: request and response bodies, status and duration, from axios, fetch, supertest and Playwright’s request fixture automatically captured. Calls made through your own API wrappers are captured too, and auth headers are redacted.
A screenshot when a test fails, taken before the browser closes.
Every retry kept separately, with tests that pass on a retry marked flaky.
Logs: Playwright steps, Cucumber Given/When/Then and console.log, each under the test it belongs to.
One HTML file, no server: attach it to a ticket or keep it as a CI artifact.

When a test fails in CI, the default report shows the assertion and the stack trace. It doesn’t show what the API returned, what was on screen, or whether the test only failed on a retry.

So I built Ace Reports. It writes one self-contained HTML file per run with all of that captured automatically.

What you get, without changing your tests:

Every API call: request and response bodies, status and duration, from axios, fetch, supertest and Playwright’s request fixture automatically captured. Calls made through your own API wrappers are captured too, and auth headers are redacted.
A screenshot when a test fails, taken before the browser closes.
Every retry kept separately, with tests that pass on a retry marked flaky.
Logs: Playwright steps, Cucumber Given/When/Then and console.log, each under the test it belongs to.
One HTML file, no server: attach it to a ticket or keep it as a CI artifact.