New series: what assistive tech really hears on your checkout page. Start with part one →
Shipwright
Home
Testing Sep 7, 2026 1 min read 380 views Updated Sep 18, 2026

Test Dashboards We Actually Look At

Sam Whitfield

Sam Whitfield

Engineering manager and recovering QA lead.…

Share
Cover illustration for the article Test Dashboards We Actually Look At

The four charts that survived after we deleted twenty others. A test suite is only valuable if the team trusts it. The moment people start re-running failures without reading them, the suite has stopped protecting anyone.

Flaky test leaderboard
Flaky test leaderboard
Suite duration over 90 days
Suite duration over 90 days
Coverage by package
Coverage by package

What the dashboards show

Reliable tests control everything outside the code under test: time, randomness, network, and fonts. Once those are fixed, a failure means something changed in the code, which is exactly what we want to know.

We have been running this approach for several months now. The initial setup took about a day, and the ongoing cost is close to zero once the team knows where to look.

None of this is new, and that is the point. The techniques that last are usually the boring ones that are documented well and supported by the platform itself.

As always, the examples are simplified to fit on a page. The production version has more error handling and logging, but the shape of the code is the same.

Questions, corrections, and war stories are welcome in the comments. Several of our best follow-up posts started as a reader pointing out something we had missed.

We will revisit this in six months with fresh numbers. If the results change, we will update the post and note what changed at the end.

What we would change next time

Questions, corrections, and war stories are welcome in the comments. Several of our best follow-up posts started as a reader pointing out something we had missed.

  • Freeze time and seed randomness in tests.
  • Quarantine flaky tests with an owner and a deadline.
  • Keep end-to-end tests for critical journeys.
  • Read every failure before re-running.
Sam Whitfield

Sam Whitfield

Author

Engineering manager and recovering QA lead. Sam writes about testing, code review, and building teams that ship calmly.

Related Posts

Comments 6

Yuki Tanaka

Any thoughts on how this interacts with server-side rendering?

Ravi Shankar

Our accessibility audit flagged exactly this last month. I wish I had read this first.

Mara Okafor Member

Would love a follow-up on how you test this in CI.

Sam Whitfield Author

It should work without shell access, you just lose the command-line shortcuts.

Sofia Rossi

Thanks for including the numbers. So many posts skip the measurement part.

Yuki Tanaka

Any thoughts on how this interacts with server-side rendering?

Leave a comment

Your email will not be published. Sign in for a faster experience.

Supports **bold**, *italic*, and `code`.