EVIDENCE
A result you can review, not just a green or red status.
RERUN keeps the signals needed to understand a browser failure while privacy mode removes common sensitive values before artifacts are written locally.
- Run-linked manifest
- Redaction before storage
- Trace opt-in only
LOCAL DOSSIER
The failed step keeps its context.
-
01
Masked screenshot
-
02
Sanitized DOM
-
03
Filtered console signals
-
04
Token-safe network URLs
Evidence layers
01 · SEE
Keep the rendered state. Mask editable regions.
Screenshots make a failure immediate, but form controls and editable regions can carry customer data. Privacy mode masks those regions before saving the image.
What the browser rendered
A visual state tied to the selected timeline step, with editable regions masked.
Written locallyStructure without captured field values
Inputs, textareas and editable content are replaced before local HTML is stored.
Useful selectors remain inspectable02 · EXPLAIN
Retain useful signals. Remove familiar secrets.
Network and console evidence can explain a failure without preserving every raw value emitted by the page.
Method and status survive
Token-like query parameters are sanitized while request method, status and useful URL structure remain.
Failure context, not a packet archiveErrors without obvious credentials
Bearer tokens, API-key patterns and familiar secret assignments are masked in captured output.
Focused debugging signal03 · DECIDE
Sensitive traces are explicit. Never a quiet default.
Full Playwright traces can include more state than ordinary evidence. Privacy mode leaves trace capture off unless a team opts in for one approved debug run.
Off in privacy mode
A sensitive trace requires deliberate activation for a specific debugging purpose.
Explicit opt-inArtifacts belong to a run
The local manifest keeps the evidence set connected to the run and its outcome.
Inspectable after replay