QA.tech + Vercel Preview Protection
This setup lets QA.tech reach Vercel preview deployments that sit behind deployment protection. It uses Vercel's Protection Bypass for Automation secret, set as domain-scoped custom headers in QA.tech Preview defaults, and bypasses password protection, Vercel Authentication, and trusted-IP restrictions for the test traffic.
What you can do
- Test password-protected preview deployments
- Keep protection on for humans, open for test agents
- Combine with per-build preview URLs from CI
Set it up
Connecting Vercel Preview Protection
- 01
In Vercel, enable Protection Bypass for Automation and copy the secret.
- 02
In QA.tech, open Settings → Applications & Envs → [application] → Preview Environments, edit Preview defaults, and add a header rule for *.vercel.app with x-vercel-protection-bypass (your secret) and x-vercel-set-bypass-cookie: true. Every new preview inherits it. Use a pattern for your own preview hostnames or custom preview domain for tighter scoping; do not put the bypass on a device preset reused on staging or production.
- 03
Run the plan against a protected preview URL to confirm the agent gets through.
Full reference in the QA.tech docs.
Where teams use this
Vercel Preview Protection in practice
This is an enabler, not a feature: it's what makes per-PR testing on Vercel previews possible at all. If tests still fail after setup, start with six ways the Vercel bypass breaks. Without it, protected previews block the agent and multi-environment setups stall at the front door. Same mechanism applies to protected feature-flag builds.
FAQ
Common questions
- Does this weaken protection for real users?
- No. The bypass applies only to requests carrying the secret headers.
Related integrations
Custom MCP Integrations
Next →Vercel Firewall
Your team moves fast. Can your testing keep up?
Our QA agents test your product autonomously, so moving fast never means shipping broken. Start free or get a 30-minute demo.