A red test can mean three very different things: the application broke, the network blinked, or the site showed a bot challenge. Most tools report all three as "failed", so teams learn to rerun reds instead of reading them.
Nexus Studio, by Verdict System LLC, gives every run one of 14 verdicts. Here is one run of seven tests and what each one said:
SECURE: passed on its own.
FLAKY: failed, then a retry passed it. Nothing was fixed.
BREACHED: the application broke. A real finding.
TIMEOUT: never answered in time.
CRASHED: the browser died.
BLOCKED: a 403, a 429 or a bot challenge.
UNREACHABLE: the host could not be reached.
Only BREACHED is a bug report. The other failures say the environment or the harness is at fault, and a retry never turns a defect into a green run.
Every failure leaves a folder of evidence: a forensic report you can read without the Studio, a screenshot, console and network data, a video for a real defect, and an optional SHA-256 chain of custody. An Executive Report turns the history into a go, caution or no-go call.
How the verdicts are decided: https://nexusstudioqa.com/docs/verdicts
By the Nexus Studio team, Verdict System LLC.
