Skip to main content
Software quality

TestProof

The test evidence tool behind our releases: every run, every step, and a document a reviewer can read without opening a spec file.

Client: In-houseTimeline: Built 2026
.NET 10BlazorSQLitePlaywright

The Challenge

A green test run tells you the tests passed. It does not tell you what they checked, whether they could have failed, or which build they ran against. When I hand over a release, “all tests passed” is a claim the client has to take on trust.

Our Approach

  1. Run. A Playwright hub runs each suite against a test or staging build. This site's suite refuses to point at production at all.
  2. Record. Two reporters write down every step of every attempt. Before they write a step, they take out what was typed and any query string.
  3. Import. TestProof reads each run into its own database: the run, each test, each attempt, each step and each screenshot.
  4. Read. The run view shows the tests, the steps of the one you pick, the step it failed at and why.
  5. Hand over. The evidence document is one self-contained file. Each result sits next to its screenshot, it lists what was left out, and it carries a fingerprint so it can be checked against the run later.

The Solution

TestProof runs table for dbs-site: 28 passed on 30 October, 21 passed and 5 failed on 28 October.
One row per run. The bar is the result: green passed, orange failed.
TestProof run view of the negative control: 5 of 5 privacy tests failed, the failing step marked, and why it failed.
The run view, on the negative control from the privacy change. The failing step is marked, and the right column says why it failed and shows the screenshot.
TestProof run view of the green run: 21 tests passed, with every step of the selected test listed.
The same view on the green run. Every step is listed, down to each check.

The preview address is hidden in these screenshots.

Results

28 of 28

passed on 30 October

21 of 21

passed on 28 October

5 of 5

failed on the negative control

3 runs of this site's suite shown here: 28 of 28 passed on 30 October, 21 of 21 passed on 28 October, and 5 of 5 failed on the negative control.

The evidence document says what it left out instead of leaving it out silently.

“A passing test proves nothing on its own. The proof is the steps, the screenshot, and a run that shows the test can fail.”