https://nexusstudioqa.com/videos?utm_source=devto#verdicts
A failed assertion, a crashed browser and a bot challenge all print the same word: failed. Nexus StudioQA gives every run one of 14 verdicts, checked in a fixed order, so the real defect is told apart from everything else.
What the video shows:
The engine rules out CRASHED, BLOCKED, UNREACHABLE and TIMEOUT before it calls a failure BREACHED.
A retry that passes reads FLAKY, and FLAKY never opens a Jira issue; an inconsistent failure reads BREACHED_FLAKY, and the issue opens.
A 403, a 429 or a CAPTCHA reads BLOCKED, never a bug report.
Seven verdicts exit 0 and seven exit 1, and every failure lands in the Evidence Locker.
Which of these reds costs your team the most time: timeouts, bot blocks or real flakes?
— the Nexus StudioQA team
Top comments (0)