How We Test Our Guides

A photo booth guide is only useful if the steps work on the device in front of the reader. This page describes how we check the advice we publish, what we can test from our own equipment, and how we describe the parts we cannot verify.

What counts as tested

We use the word tested only when an editor has run the flow on a real browser and camera and watched the result. That covers camera permission prompts, joining a room, the countdown, capture, editing, download, and share links. When a test depends on a particular device, browser version, or network condition, the guide should say which.

What we check

• That every step matches the current labels and controls in the booth.
• That a reader can complete the task without a step that only works for the author.
• That camera and microphone permission behavior matches the browser documentation we link to.
• That downloads and shared links produce the file or page the guide promises, within the seven-day retention window.
• That any claim about browser support or privacy rules is linked to the primary source.

What we cannot test

We cannot test every camera, operating system, browser build, or network. Camera drivers, corporate device policies, and experimental browser flags vary too much. We also cannot test how a specific venue, phone carrier, or printer will behave. When a result depends on those variables, the guide says so and gives a way to check it locally rather than presenting one outcome as universal.

How we handle versions

Browser menus and permission dialogs change. We review guides when we notice a change in the product or a reliable report that a step no longer matches, and we update the review date. Because the guides are written for current browsers, a guide that is several months old may describe an older menu path. The corrections page is the fastest way to tell us about a mismatch.

Evidence we prefer

1. A test we ran, with the browser and device recorded.
2. Primary documentation from the browser vendor, MDN, or Google's published policies.
3. Reproducible reports from readers, which we re-test before relying on them.

We do not use invented measurements, scores, or sample sizes. If a guide gives a number, such as a file size or a timeout, the number comes from the product or from a test we describe.

Older guides

Some guides were published before this process was written down. We are reviewing them against it and recording substantive changes. Until a guide is marked as reviewed, read its advice as general guidance and check the current browser menus where a step looks different.

Tell us what you find

If a tested step fails on your setup, send the guide URL, your browser and device, and what happened to [email protected]. We use those reports to decide what to re-test.