How we test

Payload and validation tests

Unit tests cover valid, invalid and edge-case inputs for URL, Wi-Fi, contact, message, event, location and campaign payloads. They include Unicode, reserved punctuation and unsafe URL schemes where relevant.

Render and decode checks

Representative generated symbols are decoded again locally to confirm that the rendered content matches the intended payload. SVG and PNG export paths, colour handling, quiet-zone configuration and error-correction settings are also tested.

Independent quality observations

The generator and checker assess signals such as successful decoding, foreground/background contrast, quiet zone, density and effective image resolution where measurable. A warning is not hidden by a success elsewhere, and the site does not combine the observations into a fake score.

Browser, accessibility and mobile checks

End-to-end tests cover public routes, form behaviour, errors, downloads and safety boundaries. Manual reviews include keyboard interaction, focus, labels, status messaging, mobile layouts and real-phone use of the forms.

Real-device acceptance

Approved phases have included phone-camera scans of displayed and downloaded QR codes, destination verification, contact and calendar hand-off, message composition, image upload, and mobile usability. The current outstanding launch checks are documented openly, including live-camera scanning over the production HTTPS origin and a genuine Google Business Profile review link.

Limits of any test

Scan performance also depends on the final size, printer, material, damage, glare, lighting, camera and scanning application. For important work, test a final production proof with several real devices in the intended environment.