Your tests stay Playwright, Selenium and pytest. We don't replace them. We make them enterprise-ready, and you own your code, your evidence and your history.

Go/No-Go release decision from your test runs.

The Nexus StudioQA Executive Report turns your test history into a release decision. It averages a stability score across your tests, then says Go when the score is at least 90 and no failure is open, Caution when the score is at least 70, and No-Go below that. The report prints each criterion with its measured value.

By the Nexus StudioQA team, Verdict System LLC.

Last updated: .

The rule, exactly

DecisionRuleReport wording
GoConfidence score of 90 or more and no open failuresRelease: go
CautionConfidence score of 70 or more, when Go is not metRelease: caution
No-GoConfidence score below 70Release: no-go

The thresholds 90 and 70 are fixed numbers in the report code, not settings. The cover and the summary list the three criteria with the value measured for each one, so a No-Go says which criterion failed instead of only showing red.

Where the score comes from

Each test gets a stability label from its History. The confidence score is the mean of those labels, rounded.

LabelPointsWhen History gives it
STABLE100Pass rate of 90% or more and a flaky rate under 5%
UNSTABLE70Pass rate of 70% or more
FLAKY40Below that, with a flaky rate of 15% or more
CRITICAL0Everything else

A flaky run counts as flaky, not as a pass, so a test that only passes on retries pulls the score down. Open failures are the failure records in the evidence folder that are not ruled out as a false alarm and not fixed since.

What the Executive Report contains

The report is built from the evidence on your machine and opens as HTML, with a PDF export. It has an executive summary with the previous period for comparison, a daily trend, a risk register ranked by severity, coverage by area, open failures with their root cause, test stability, durations and error categories, recommendations, a sign-off page and an appendix. You can scope it to the last 7, 30 or 90 days, to the full history, or to a date range.

Common questions

  • Can I change the 90 and 70 thresholds?

    No. They are fixed in the report code. What you control is the window the report covers and which failures are ruled out as false alarms.

  • Does one open failure block a Go?

    Yes. Go needs a score of at least 90 and zero open failures. With one open failure the best result is Caution, as long as the score is at least 70.

  • Does the report need an internet connection?

    No. It is built from tests, results and evidence on your own machine. The only connection the Studio makes on its own is the license check.

  • Is the decision a replacement for a human sign-off?

    No. It is an input. The report has a sign-off page for the person who decides, and its recommendations list what to check before release.

Get a release decision with its evidence.

Everything runs on your own machines. No card needed.