test-staging-branch

Automate end-to-end testing of Vercel preview deployments with Chrome and Gmail OTP.

249|47|Updated Nov 5, 2024
One-click install
npx skills add https://github.com/different-ai/agent-bank --skill test-staging-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-staging-branch
Source: https://github.com/different-ai/agent-bank/tree/main/.opencode/skill/test-staging-branch
Command: npx skills add https://github.com/different-ai/agent-bank --skill test-staging-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end testing of staging feature branches on Vercel preview deployments by leveraging Chrome automation and Gmail OTP flows, reducing manual validation time and improving test reliability.

Core Features & Use Cases

  • End-to-end validation of PR-based previews, including deployment readiness, automated login via Gmail OTP, feature-specific checks, and result reporting to GitHub.
  • Deterministic testing patterns that minimize expensive UI snapshots while ensuring coverage of critical paths.
  • Reusable workflow steps documented in SKILL.md that can be adapted for different branches or features.

Quick Start

Use the test-staging-branch Skill to validate a PR's staging branch by following the steps outlined in SKILL.md. Provide the deployment URL to begin automated testing, and review the GitHub PR comments for test results.

Frequently Asked Questions about test-staging-branch

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

FAQPage Schema
How do I automate end-to-end testing of staging branches on Vercel preview deployments?

You can automate staging branch testing by providing a Vercel preview deployment URL to trigger Chrome automation, perform Gmail OTP login, run feature checks, and report results to GitHub PRs.

How does Gmail OTP login work during automated testing of preview deployments?

Gmail OTP login is automated by accessing Gmail programmatically to retrieve one-time passwords, then entering them into the Vercel preview deployment interface via Chrome automation.

What tools do I need to run automated tests on Vercel preview deployments with GitHub PR reporting?

You need Chrome DevTools MCP, Vercel CLI authenticated with a scoped project, Gmail access, and GitHub CLI to execute the automated testing workflow and report results.

What is the best way to validate PR-based staging previews without manual UI snapshots?

Deterministic testing patterns minimize expensive UI snapshots while ensuring coverage of critical paths by automating feature-specific checks and deployment readiness validation for Vercel previews.

How do I report automated test results back to a GitHub PR from a Vercel staging branch?

Automated test results are reported to GitHub PRs using the GitHub CLI, posting validation outcomes for Vercel preview deployments directly as comments on the corresponding pull request.