How preview deployment checks work
TestForge treats each Vercel preview URL as the target for your recorded flow. The goal is the same check on every PR, before code reaches production.
When GitHub Actions (or the Vercel integration) runs, it resolves the unique preview URL for the deployment under test. That URL is passed into the runner (for example via TESTFORGE_BASE_URL) so Playwright opens the preview build, not production.
Typical setup runs on pull_request or on deployment_status when Vercel marks a preview as ready. You want the test to start after the preview is reachable, avoiding flaky “site not up” failures.
You record flows once. Each run replays those steps against the current preview instance. Branch-specific data should either be stable in preview or mocked at the app layer so the flow stays repeatable.
Pass/fail should be visible where the team already works: CI checks on the PR, and optionally Slack or email from your notification settings. The dashboard retains history, failed steps, and screenshots for debugging.