Recordings
Every run is recorded end to end. Download the video, screenshots and logs from the Actions section of a test attempt.
Every run is recorded end to end — a full-motion replay of UI actions, transitions and responses, downloadable per test attempt.
Platforms
Android · iOS
Recorded
Every run, automatically. Nothing to enable
Download from
The Actions section of a test attempt
Also there
Screenshots and execution logs
Watch out
Secure screens render black in the recording. The OS blocks capture there
Prerequisites
A completed run, local or cloud
The specific test attempt you want artifacts for — each attempt has its own set
Download the artifacts
Open the run.
Open the test attempt.
Open the Actions section.
Download the recording, the screenshots or the execution logs.
Confirm the downloaded file opens. Report links are signed and time-limited; the downloaded file is not.
Recording
The full run, replayable frame by frame
Screenshots
The before and after images for every step
Execution logs
Timestamped, step by step, with what Drizz decided at each one
Each test attempt has its own set. A test that ran three times in a plan has three recordings.
What a recording shows that a screenshot cannot
Transient UI
A toast, error banner or loader that appeared and went between screenshots
Animation and timing
A screen still settling when the step ran
Unexpected navigation
A tap that opened something and closed it again
Failures that don't reproduce locally
Diagnose from the recording rather than rebuilding the scenario
Shared evidence
QA, engineering and product review the same footage
Audit trail
A verifiable artifact of exactly what ran
Secure screens
Rendered black. The OS blocks capture there
Read the report first, recording second. The before-screenshot of the first failing step resolves most failures on its own — see When a step fails.
Retention
Report links are signed and time-limited, and so is access to the artifacts behind them. A recording that is evidence for a bug report or a release decision has to be downloaded and attached as a file.
Common mistakes
Link a recording in a ticket instead of attaching it
The link expires and the ticket loses its evidence
Open the recording before reading the report
You watch four minutes of video to find what one screenshot showed
Report a black section as a broken recording
Secure screens block capture. Nothing was recorded to lose
Download from the plan rather than the attempt
Artifacts are per test attempt. A re-run has its own set
Next
Last updated: 6 August 2026
Last updated
Was this helpful?