Menu

Proof that your software is tested, from your own CI

A green pipeline doesn't say which tests ran, on which code, and whether that was the code that went live. We read the evidence from your own CI and show, per commit and per release, what is provably tested.

Join the pilot

Updated

Evidence in five steps

Take your end-to-end tests. Step by step we look at how far the evidence reaches. A claim without a report counts as not proven.

  • A test suite exists
  • It ran on this commit: a CI run with its report, such as JUnit XML, a Playwright or Cypress report, or a coverage file
  • It passed
  • It also ran for the commit that went live
  • It covers your application's most important flows, as your specification or documentation names them

What you see for each check

Every check gets a label with an icon, never colour alone, and a link to its evidence: the run, the report and the commit.

  • Tested by you, checked by us: the report belongs to this commit and passed
  • Reported by you, not checked: there is a claim or a report, but it doesn't belong to this commit, is old or can't be checked
  • Not proven or failed: no evidence, or it fails, with the reason
  • Not applicable

Why we take the evidence from your CI

You already test. We don't put a second test setup next to it that works differently; we check whether the evidence is there and holds. You build and test, we show what is proven.

Which pipelines and reports count, you agree with us in your workspace's chat. We only get read access.

Questions we often get

Do you run our tests yourselves?

Not now. We read the evidence from your own CI, which is usually already there. That way we check what you really ran, on the code that really went live.

What if we have no end-to-end tests?

Then it says 'Not proven', with the reason. That's not a reproach: it shows where evidence is missing, so you know where to start.

Do you measure test coverage?

If your CI produces a coverage file, we read it and link it to the commit. A number doesn't tell the whole story, though. So we also look at whether the most important flows have a test.

Which CI can you read?

The major systems: GitHub Actions, Azure DevOps, GitLab CI and Bitbucket Pipelines, always with read access only. If you use something else, put it in your sign-up.

Sign up for the pilot

The pilot is by invitation. Sign up, we check whether your application fits and email you. You connect your repository with read access only, the first check starts by itself, you see what is checked and what is proven, and then we ask what it is worth to you. Have a question first? Ask it in the message below.

Our team

Reads every sign-up and every question

Our team reads what you send and answers by email. A conversation only happens if you ask for one: with the people who do the work, not a salesperson.

We only use your details to respond to your sign-up. The website doesn't keep your request.