// docs
Evidence & redaction
A rolling buffer records steps, network and console for the run; a fail promotes it into a redacted bundle. Inputs are masked and auth headers redacted before anything is stored. Pixel-level media redaction is not built.
The point of a Teasynaer run is that a failure leaves with enough evidence to re-check it later, instead of a note you have to reconstruct from memory. Here is exactly what is captured, what is masked, and where it lives — no more and no less.
Always on
For the whole run, without any extra setup, Teasynaer records:
- the step trail — the cases you worked and the pass/fail/skip verdict on each, and
- the environment — the real browser, OS and viewport the pass ran in.
From the Runner tab
A rolling buffer also captures network (HAR) and console activity — but only the HTTP calls and
console output made inside the Runner tab itself (an always-on fetch patch). If you exercise an
application in a separate tab or window, that traffic does not appear in the HAR. Capturing the
app under test across a separate tab is the job of the optional Connect browser extension;
without it, network/console evidence reflects the Runner tab.
Screenshots & clips — you press the button
Screenshots and the screen clip are manual: in the Runner you click Shot or Record
and grant screen-share (getDisplayMedia / MediaRecorder), then perform the steps in the shared
window. Recording auto-stops and attaches when you mark the case failed. There is no hidden
always-recording; if you never click Record, there is no clip. Recording size is bounded by
QA_MAX_RECORDING_MB.
Redaction — text, not pixels
On a fail the buffer is promoted into a bundle — HAR, console errors, the screenshots and clip you grabbed, and the environment — written to the evidence volume and attached to the tracker issue. Before anything is stored, the redaction pass masks text inputs and drops sensitive auth headers (they are removed, not mask-and-kept).
Pixels are not redacted. A screenshot or screen recording is stored as captured — if a secret was visible on screen, it is visible in the bundle. Pixel-level redaction (blur/blackout baked into the stored artefact) and per-deck redaction rules are on the roadmap, not shipped yet. Treat screenshots and clips accordingly, and prefer the export packet for anything you want to review before it reaches a tracker.