vercel-e2e-test

Deploy Vercel previews and run Playwright tests against staging.

30|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/enbyaugust/zacs-claude-skills --skill vercel-e2e-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vercel-e2e-test
Source: https://github.com/enbyaugust/zacs-claude-skills/tree/main/skills/vercel-e2e-test
Command: npx skills add https://github.com/enbyaugust/zacs-claude-skills --skill vercel-e2e-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end testing for Vercel previews by deploying a preview and executing Playwright tests against a staging environment, ensuring that new changes meet quality gates before going live.

Core Features & Use Cases

  • Deploy to a Vercel preview and capture the preview URL.
  • Start and coordinate local worker and edge functions for test environments.
  • Run Playwright test projects across multiple configurations (chromium variants) and report results.
  • Use in CI or local development to validate changes quickly and reliably.

Quick Start

Deploy a Vercel preview, then run the full Playwright suite against the preview URL.

  • npx vercel
  • Use a captured PREVIEW_URL with:
  • cross-env PLAYWRIGHT_BASE_URL="<preview-url>" npx playwright test --project=chromium --project=chromium-clean --project=chromium-admin --project=chromium-with-worker --project=chromium-with-edge-functions --retries=2

Frequently Asked Questions about vercel-e2e-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Playwright E2E tests against a Vercel preview deployment?

To run Playwright E2E tests against a Vercel preview, deploy your changes via the Vercel CLI, capture the generated PREVIEW_URL, and execute cross-env PLAYWRIGHT_BASE_URL="<preview-url>" npx playwright test.

What is the best way to automate deployment validation in a Vercel CI pipeline?

Automating deployment validation in a Vercel CI pipeline is best achieved by deploying a preview, capturing the URL, and running Playwright test projects across multiple configurations to ensure changes meet quality gates.

Do I need cross-env to coordinate Vercel preview testing with Playwright?

Yes, cross-env is required to set the PLAYWRIGHT_BASE_URL environment variable dynamically, allowing you to pass the captured Vercel preview URL directly into the Playwright test execution command.

Can I run multiple Playwright test projects against a Vercel staging environment?

Yes, you can run multiple Playwright test projects like chromium, chromium-clean, and chromium-admin against your Vercel staging environment by specifying each project in the test command with retries.

How do Vercel preview deployments coordinate with local worker and edge functions for testing?

Vercel preview deployments coordinate with local worker and edge functions by starting and orchestrating them during test execution, ensuring the staging environment accurately reflects production behavior for Playwright tests.

What are the limitations of using Vercel previews for local end-to-end test verification?

Using Vercel previews for local end-to-end test verification requires the Vercel CLI, Playwright, and cross-env to orchestrate deployment and execution, meaning local environments lacking these dependencies cannot run the validation workflow.