LAUNCH QA · BROWSERS + DEVICES

“Works on my computer” is not a launch strategy.

Record real browser/device smoke tests, capture failures with reproducible details, and see which launch environments still have no evidence.

TEST NOW — THIS BUILDRecord browser/device smoke runs only on browsers and devices you actually use. Log real defects, export the QA JSON, and leave unsupported environments uncovered rather than guessing.

PRODUCTION LATER — LEAVE NOT CHECKEDThe Production Smoke Checklist is for the real domain, auth, data, payment, email, uploads, backups, logging, rate limits and privacy workflows. On clarawidetest, leave these blank.

RECORD THIS TEST

Browser / device smoke result

MINIMUM LAUNCH COVERAGE

Core browser / platform matrix

These are the minimum environments ClaraWide should have real passing evidence for before launch approval.

PRODUCTION SMOKE CHECKLIST

Things the static test site cannot prove

Record these only after testing the actual production environment they describe. If you click one by mistake, use Clear / Not Checked instead of manufacturing a result.

ISSUE LOG

Capture the failure before fixing it

OPEN FINDINGS

Launch blockers & defects

RECENT SMOKE RUNS

Evidence by browser and device

NEXT LAUNCH LAYER

Performance & animation QA

Once browser/device coverage is being recorded, use route timing, controlled mobile runs, motion budgets, and reduced-motion checks to catch slow or janky experiences.

Open Performance QA →

Sign-off boundaryThis page organizes evidence; it does not manufacture it. Browser/Device or Production Smoke QA should not be marked complete until supported browsers/devices and production-domain flows have actually been tested and unresolved Critical/High issues are closed or explicitly launch-waived.