The build failed. What’s different this time?

Keep results from your test runner together across builds. Compare recent outcomes, open the failed test’s history and read the failure details included in its report.

See whether failures are increasing

Review passed, failed and skipped totals across recent results. Compare them with the amount of testing recorded before deciding where to dig in.

Keep your runner. Bring the reports together

Upload JUnit XML, Playwright JSON or Mocha JSON reports, or send them through the API. Review the imported tests without changing how you run them.

Local reports

Keep local results in the same history as CI results, so the evidence does not stay on one person’s machine.

CI through the API

Send supported reports through the API so later reviews do not depend on finding the original build artefact.

Follow a results file through to the tests

See how an upload connects to its results file, the run it created, and the suite and test results recorded in that run.

Start with the failed test

See whether the test failed before, how often it passes and what its latest result reported. Keep earlier outcomes and failure details together while you investigate.