Replay videos
Every run of a recorded test leaves a video made to be watched. You choose how it is paced.
What the video shows
A replay has no mouse and types a whole field at once, so a raw recording is hard to follow. verifAIed draws in what is missing:
- A cursor that glides to each element before the step uses it.
- A mark on the element and on the click point, held for a moment before the action.
- Text typed into a field a few characters a second, not all in one frame.
- A caption for each step: a short line in plain English at the bottom of the frame.
- A hold after each check, so you see the state that was checked.
Captions and holds belong to the test. You set them while recording or editing. See Captions and holds.
The three paces
| Pace | What you get |
|---|---|
| Fast | The default. The cursor, the marks, typing at a readable pace, captions, and the pauses and holds the test asks for. |
| Watch | Lingers on every step. Slower to run, easiest to follow. |
| Off | No cursor, no marks, instant typing, no pauses or holds, no captions. The quickest run and the hardest to review. |
Choose for one run
On the web, open Video settings next to Run all on the Browser Tests page, or next to Run on a test's page. It has two choices, and both start on Repo default:
- How these runs record: Off, Fast or Watch.
- Test title banner: whether the test's name is shown in a corner of the video.
The choice is remembered in your browser. It applies to every run you start from the web until you set it back to Repo default. From the terminal, pass the pace to one run:
verifaied test run "Settings/API tokens" --video watch
Set the defaults for a repository
Set them on the repository's Settings page under Browser tests. They apply to everyone and every machine. See Repository settings.
Or set them in .verifaied/config.toml, under [browser-tests]. These are the keys, with their defaults:
[browser-tests] # Each of these can also be set on the repository's Settings page, which # applies to every machine and wins over this file; this file decides # for a key the page leaves unset. # How long each step holds the element it is about to act on — lit, with # the click point marked — before acting. This is what makes a video # something you can actually review. 0 turns the marking off. replay_show_actions_ms = 250 # An extra dwell after every operation, on a page with nothing marked. # 0 by default: the pause above says more for the same millisecond. replay_slow_mo_ms = 0 # The cursor. A replay has no mouse, so one is drawn and glides to each # element before it is acted on. A move across the page takes this long; # shorter moves take less. 0 draws none. replay_cursor_ms = 400 # Typing. A filled field is typed one key every this many milliseconds — # 200 is five characters a second. 0 fills it whole, in one frame. replay_type_delay_ms = 200 # Whether the Pause steps a flow asks for, and the holds after its # checks, actually wait. The off video profile skips them for one run; # false skips them in every run from here. replay_pauses = true # Whether each step's caption is drawn on the video as it runs. The off # video profile leaves them out for one run. replay_captions = true # The replay's page size — and its video's, pixel for pixel. replay_viewport = "1280x900" # Name the test in a corner of the video, for the whole run. replay_video_step_banner = true # A run nobody watches — headless, from the web or CI — goes at full # speed, and its video is paced afterwards with everything above. false # paces every run live instead. A run in a window is always paced live. replay_render = true # How the studio authors a recording. Every new check holds the video # this long after it passes, so the viewer sees what was checked — 0 for # no hold. Any check can be given its own from its Edit form. assertion_pause_ms = 2000 # Whether steps are captioned as they land: a short line, in plain # English, drawn over the video. Any step's caption can be edited, # regenerated or switched off from the flow. captions = true
When a setting has more than one value, a choice for one run wins over the Settings page, and the Settings page wins over the file.
Single runs and batch runs
Pacing is time the browser spends waiting. So verifAIed paces a run live only when somebody is about to watch it.
- A single test is paced live: a test you just recorded, one Run on the web, or one test named in
verifaied test run. - A batch runs at full speed: Run all, a folder's Run,
--all,--folderand CI. Its paced video is put together after the run, from the run's own frames, following the same settings.
A video put together afterwards holds the page still through each pause, so on a page that animates it is less smooth than a live one. For that reason the test keeps its last live-paced video even after later batch runs. The test's page plays that video, says which run it is from, and offers Show the newest run's video. The result and the trace shown are always the newest run's.
To pace every run live, switch off Speed up runs nobody is watching on the Settings page, or set replay_render = false. For one run, use --no-render or --render.
Watch a video
Open a test and click a run. The video plays beside the flow.
- Playback speed is 0.25×, 0.5× or 1×. Your choice is remembered.
- Open trace opens the run in Playwright's trace viewer.
Good to know
- verifAIed keeps the newest replay of each test per branch on Free and Basic, and the newest 5 on Pro. See Plans and limits.
- A test that opens a popup or a second page, or resizes its own window, is always paced live.
- If a video cannot be paced after a run, the plain video is kept and labelled unpaced.
- Pause steps always wait, unless the pace is Off.