How to record a good video

The better the video, the better the test. A good recording is short, shows one flow clearly, and ends on visible proof that the flow worked.

The checklist

• One flow per video, with one clear outcome
• Starts on a known page, ideally with the address bar visible
• Normal pace, with a short pause after each page change
• Ends on proof: stay on the result for 2 to 3 seconds
• Test data only: a test account, test card numbers, made-up names
• MP4 or WebM, within your plan's size and length limits

One flow, one outcome

"Sign up, create a project, invite a teammate and upgrade the plan" is four tests, not one. Split it. Short tests fail for one reason, which makes failures quick to understand, and you can run them in any order.

A good rule: if you'd describe the flow with "and then" more than twice, it's probably two videos.

Show where you start

If the browser's address bar is visible at the start, ReplayQA reads the starting page from it. If you crop it out or record a full-screen app, enter the Page the video starts on when you upload.

Move at a normal pace

There's no need to go slowly, but:

• Pause briefly after each click that loads something new, so the next screen is visible in the video.
• Type values in full rather than picking from browser autofill, so the typed text is visible.
• Close cookie banners and pop-ups on camera if they appear, so the test knows to close them too.

End on proof

The last few seconds of the video become the test's final check, so make them count:

Logins and passwords

You can record yourself logging in. ReplayQA never reads passwords from the video (they show as dots anyway). It asks for the password once and stores it encrypted. See Test logins and passwords.

If many of your flows start signed in, record one short sign-in video and set it as the site's sign-in test, and every other test signs in first.

Data that changes

Tests run again and again, so think about what changes:

• Unique values: if a flow creates "Project A" and names must be unique, the second run fails. Prefer flows that edit or check existing data, or that tolerate duplicates.
• Dates: a booking for "tomorrow" means a specific date in the test. See Dates, dropdowns and popups.
• Destructive actions: deleting or paying for something really happens when the test runs. ReplayQA asks you to confirm these steps and blocks them on sites marked as production.