QA Reef for Vercel.
Every deployment gets crawled twice: pre-promote as a blocking check, and again in production after.
What the check does
It crawls the deployment from the root, same-origin, up to 50 pages:
- Broken internal links, 4xx/5xx pages, failed and blocked requests
- Console errors and uncaught exceptions
- Missing title, h1 or meta description; mixed content; page weight
- Load timing, FCP / LCP / CLS / TBT when observed
- Full-page screenshots, pixel-diffed against the previous deployment
- Recorded flows, replayed against the deployment URL
A critical finding fails the check and blocks the promote, linked to a report with the evidence.
How to run it
Vercel integration
Checks appear on every preview and production deploy.
CLI or GitHub Action
Call the hosted API from CI, gate the job on the verdict.
qareef vercel-check --url https://my-app-abc123.vercel.appProtected previews: give QA Reef the project's Protection Bypass for Automation secret, scoped to that deployment's origin. Without it, a protected preview fails as a critical finding, not a silent pass.
Writing the suite behind the check: end-to-end testing for Next.js apps, including the bypass headers and how public Next.js suites handle login and seeding.
Status
Built and tested; not yet listed on the Vercel Marketplace. Checks run on the same browser-minute plans as the rest of QA Reef: see pricing.