I built a free HTML test reporter for that automatically captures API calls, screenshots and retries

I built a free HTML test reporter for that automatically captures API calls, screenshots and retries

●1 ●3 ●8
calendar_today ago • schedule2 min read

When a test fails in CI, I usually end up asking the same questions:

What did the API actually return?
What was on the screen when it failed?
Did it fail on the first try, or only on the retry?
Is this test flaky, or did something really break?

The default reports show the assertion and the stack trace, so the rest means adding console.logs, rerunning locally, or digging through traces.

So I built Ace Reports: one self-contained HTML file per run, with all of that captured automatically. It already existed for .NET, Java and Python, and it’s now on npm for TypeScript/JavaScript.

Live demo report: https://harshadlambate.github.io/AceReportsWebsite/demo.html

What it captures, without changing your tests.
Every API call: method, URL, request and response bodies, status and duration. It hooks Node’s http/https and the global fetch, so it covers axios, fetch, got, supertest, node-fetch, ky and Playwright’s request fixture. It also covers calls made through your own API client wrappers and vendor SDKs, with nothing to wrap. Authorization and cookie headers are redacted.
A screenshot on failure, taken before teardown closes the browser. It finds the page by itself: Playwright’s page fixture, a Vitest test.extend page, a Cucumber World’s this.page, or the jest-playwright global.
Retries and flaky tests: every attempt is its own tab with its own logs, error, API calls and screenshots. A test that passes after a failed attempt is marked flaky instead of quietly showing green.
Logs: Playwright test.step, actions and expects. Cucumber Given/When/Then steps, with doc strings and data tables. console.log output, placed under the test that wrote it.
Search, filters and categories: filter by status or tag, search by name, and click a category bar to narrow the table.
One HTML file, no server: attach it to a ticket, email it, or keep it as a CI artifact.
How to use it: Please follow the readme file: https://github.com/HarshadLambate/AceReportsWebsite

It’s free to use, including at work.

Website: https://harshadlambate.github.io/AceReportsWebsite/

I’d really like feedback: what’s missing from your current test reports, and which HTTP client or framework should I support next?

Want more #productivity & #playwright deep dives?

Join 5,958+ developers sharing real benchmarks, code breakdowns, and projects. Free forever.

9 Comments

2 votes
1
2
1
1 vote
1
1 vote
0
0 votes

More Posts

I’m a Senior Dev and I’ve Forgotten How to Think Without a Prompt

Karol Modelski - Mar 19

How I Built a React Portfolio in 7 Days That Landed ₹1.2L in Freelance Work

Dharanidharan - Feb 9

TypeScript Complexity Has Finally Reached the Point of Total Absurdity

Karol Modelski - Apr 23

Three Design-to-Code Rules Most Developers Ignore (That Will Make You a Better Engineer)

Joemetry - Sep 26

I Wrote a Script to Fix Audible's Unreadable PDF Filenames

snapsynapseverified - Apr 20
chevron_left
185 Points • 12 Badges
2Posts
4Comments
3Connections
I’m a software engineer passionate about building open-source tools that solve real problems and mak... Show more

Related Jobs

View all jobs →

Commenters (This Week)

5 comments
2 comments
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!