Example release verification report

14 pull requests merged. One risky workflow had no test.

This illustrative example shows the kind of evidence a release verification returns. The application, pull requests and results in this report are synthetic.

3 of 9

Workflows assessed

1

Gap found

2 of 2

Detected simulated failures

4

Open checks

The gap, in plain words

If a card payment times out and retries, the order must stay unpaid until the payment is confirmed. The combined changes in this example had no test for that workflow.

The test and its evidence

The new test passes on the original build and fails at the expected assertion when valid simulated failures are introduced. One non-compiling trial is not counted as proof.

What you get back

A reviewable test patch, an evidence receipt and run logs. The release decision stays with your team.

Start with a real pull request

Get a report built around your own release.

Bring one real change. We’ll help you find the evidence worth reviewing.

Evaluate one PR