AGENT SKILL

e2e-testing

End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
e2e-testing
risk
safe
source
personal
category
granular-workflow-bundle
date_added
2026-02-27
description
End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.

03 SKILL.md 正文

E2E Testing Workflow

Overview

Specialized workflow for end-to-end testing using Playwright including browser automation, visual regression testing, cross-browser testing, and CI/CD integration.

When to Use This Workflow

Use this workflow when:

  • Setting up E2E testing
  • Automating browser tests
  • Implementing visual regression
  • Testing across browsers
  • Integrating tests with CI/CD

Workflow Phases

Phase 1: Test Setup

Skills to Invoke

  • playwright-skill - Playwright setup
  • e2e-testing-patterns - E2E patterns

Actions

  1. Install Playwright
  2. Configure test framework
  3. Set up test directory
  4. Configure browsers
  5. Create base test setup

Copy-Paste Prompts

Use @playwright-skill to set up Playwright testing

Phase 2: Test Design

Skills to Invoke

  • e2e-testing-patterns - Test patterns
  • test-automator - Test automation

Actions

  1. Identify critical flows
  2. Design test scenarios
  3. Plan test data
  4. Create page objects
  5. Set up fixtures

Copy-Paste Prompts

Use @e2e-testing-patterns to design E2E test strategy

Phase 3: Test Implementation

Skills to Invoke

  • playwright-skill - Playwright tests
  • webapp-testing - Web app testing

Actions

  1. Write test scripts
  2. Add assertions
  3. Implement waits
  4. Handle dynamic content
  5. Add error handling

Copy-Paste Prompts

Use @playwright-skill to write E2E test scripts

Phase 4: Browser Automation

Skills to Invoke

  • browser-automation - Browser automation
  • playwright-skill - Playwright features

Actions

  1. Configure headless mode
  2. Set up screenshots
  3. Implement video recording
  4. Add trace collection
  5. Configure mobile emulation

Copy-Paste Prompts

Use @browser-automation to automate browser interactions

Phase 5: Visual Regression

Skills to Invoke

  • playwright-skill - Visual testing
  • ui-visual-validator - Visual validation

Actions

  1. Set up visual testing
  2. Create baseline images
  3. Add visual assertions
  4. Configure thresholds
  5. Review differences

Copy-Paste Prompts

Use @playwright-skill to implement visual regression testing

Phase 6: Cross-Browser Testing

Skills to Invoke

  • playwright-skill - Multi-browser
  • webapp-testing - Browser testing

Actions

  1. Configure Chromium
  2. Add Firefox tests
  3. Add WebKit tests
  4. Test mobile browsers
  5. Compare results

Copy-Paste Prompts

Use @playwright-skill to run cross-browser tests

Phase 7: CI/CD Integration

Skills to Invoke

  • github-actions-templates - GitHub Actions
  • cicd-automation-workflow-automate - CI/CD

Actions

  1. Create CI workflow
  2. Configure parallel execution
  3. Set up artifacts
  4. Add reporting
  5. Configure notifications

Copy-Paste Prompts

Use @github-actions-templates to integrate E2E tests with CI

Quality Gates

  • [ ] Tests passing
  • [ ] Coverage adequate
  • [ ] Visual tests stable
  • [ ] Cross-browser verified
  • [ ] CI integration working

Related Workflow Bundles

  • testing-qa - Testing workflow
  • development - Development
  • web-performance-optimization - Performance

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1