Statuses

What Passed, Passed (healed), Failed, Error and Blocked each mean, and why infrastructure failures now report as Error.

A run reports one of five statuses. Two of them — Error and Blocked — are not test results.

Statuses	Passed · Passed (healed) · Failed · Error · Blocked
Your test's fault	Failed, and only Failed
Not your test	Error (infrastructure) · Blocked (billing)
Green but not clean	Passed (healed) — check which steps needed repair
Watch out	Infrastructure failures now report as Error, not Cancelled

Prerequisites

None.

Status reference

Status	Meaning	Cause	Action
Passed	Every step succeeded first time	—	None
Passed (healed)	Succeeded, but one or more steps were repaired mid-run	A step description no longer matches the screen	Read the healed list and rewrite those descriptions — see Self-healing
Failed	A step failed and could not be recovered	The test, the app, or the screen state	Triage it — see When a step fails
Error	Something outside the test went wrong. Most commonly a device could not be allocated	Infrastructure. Nothing in the script caused it	Re-run. If it recurs, it's device capacity — see Devices
Blocked	The run was stopped for a billing reason and never started	Wallet out of credit. It does not always present as a billing message	Check the wallet balance and top up — see Billing & tokens

Common mistakes

What you do	What happens
Still parsing Cancelled	Every infrastructure failure is missing from your numbers
Debug an Error as a test failure	You investigate a script that never ran
Count Passed (healed) as Passed in a pass-rate metric	The metric hides a degrading suite
Treat Blocked as a platform outage	It's the wallet. Check the balance first
Re-run a Failed test hoping it passes	A description failure is deterministic. Read the before-screenshot

Next

• When a step fails

• Reading a report

• Self-healing

---

Last updated: 6 August 2026