Execution health
Recorded outcomesclean pass rate
Test runs/
Execution intelligence
Execution overview
Health, runtime context and cases worth reviewing.
Run context
ReproducibilitySlowest tests
Select for evidenceAttention needed
Test explorer
Explicit assertions · recorded evidence
| Test case | Outcome | Steps | Duration |
|---|
No matching cases
Try another search or clear the outcome filter.
Healing audit
Review locator changes while preserving the original assertions.
↻
No locator repairs recorded
This run contains no healing records. Case outcomes and expected values remain exactly as recorded by the runner.
Environment & provenance
The runtime and source data behind this execution.
Recorded environment
View raw environment JSON
Evidence and interpretation
Results reflect actual runner outcomes. Healed cases remain separately classified; setup and teardown failures fail the case.
Screenshots and trace files are relative to this report folder. Keep them together when sharing the offline report.
Native screenshots need a visible, unlocked desktop. Open web/Electron trace ZIPs with Playwright Trace Viewer.
Requirement mapping describes the linked cases. Review acceptance criteria and untested business rules before claiming product acceptance.
Layers & timings
Measured requests, queries and UI checks across the same journey.
Execution by layer
| Layer | Steps | Clean / healed | Failed / skipped | Total step time |
|---|
Timing evidence
API request time includes receipt of the body. Query time excludes connection setup. UI action time excludes screenshot capture. Values come from this run; they are not load-test percentiles.
| Case / step | Layer / target | Measurement | Duration | Evidence |
|---|
Execution policy
Effective restrictions after combining the plan and suite.
Do / don't rules and enforced restrictions
Methods, target/action denials, approved origins and screenshot permission are structured restrictions. Database checks expose reads only. Text notes describe user intent and require matching assertions or review; arbitrary prose cannot be enforced automatically.
API/database JSON evidence is redacted by known secrets and key names. Screenshots can still contain application data; disable capture when required and review artifacts before sharing.