Actionable Reports

146 tests failed. Which ones need you?

Most of these failures are ones you've already triaged. Allure TestOps links them to known issues automatically, and you handle the rest in the same test run.

Start free trial

No credit card required

Test run 842, Storefront regression, as it lands: 146 failed and 2,254 passed tests, with failed tests such as Complete checkout with a saved Visa card and Refund a captured payment, and 141 more

Known issues

Triage once. Not every run.

Failures that match a known issue are linked to it automatically. Muted tests still run, but they don't affect the success rate. Only 14 failures still need you, and some look flaky.

Test run overview: four open defects with 52, 34, 22, and 12 linked failures, 12 muted tests, and the 14 unresolved failures that remain

Rerun selected tests

Rerun the suspects. Not the whole suite.

Rerun just those tests through CI. In this run, the full regression takes 40 minutes and the suspects are back in three. Their retries land in the same test run, next to the original failures. Six pass, and eight failures remain.

Failure investigation

Eight new failures. Now look closely.

Open a failed test and follow its scenario to the step that broke, with the error and the screenshot your test attached. You understand the failure before you try to reproduce it.

Failed test result for Complete checkout with a saved Visa card: sign-in and cart steps passed, and the payment step failed waiting for the order confirmation, with the timeout error and a failure screenshot attached

Then look around the failure.

Compare branches, see what ran alongside it, and check its history to tell a product bug from an environment problem. Seven of the eight share one checkout error.

Compare this test run with runs on other branches to see where the failure appears.

Test Run Compare of run 842 on main against release/2.19 and release/2.18: the seven checkout timeouts fail only on main, a known payment gateway failure fails on all three branches, and two unrelated tests fail on one release each

Defects

Save what you found. The next run will know.

Fifteen minutes on this error today. None in the next run. Save it as a defect, and the seven failures no longer need you. They stay failed until a developer fixes the bug.

Manual rerun

Automation broke. The release can't wait.

The last test broke on a changed checkout page, not on a product bug. Rerun it manually and the release goes ahead today, with the failed automated attempt kept beside it as a retry.

Zero unresolved. Your next run starts here.

In the next run, failures that match your defects are linked automatically. Try it on your own pipeline.