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 setupe2e-testing-patterns- E2E patterns
Actions
- Install Playwright
- Configure test framework
- Set up test directory
- Configure browsers
- 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 patternstest-automator- Test automation
Actions
- Identify critical flows
- Design test scenarios
- Plan test data
- Create page objects
- 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 testswebapp-testing- Web app testing
Actions
- Write test scripts
- Add assertions
- Implement waits
- Handle dynamic content
- Add error handling
Copy-Paste Prompts
Use @playwright-skill to write E2E test scripts
Phase 4: Browser Automation
Skills to Invoke
browser-automation- Browser automationplaywright-skill- Playwright features
Actions
- Configure headless mode
- Set up screenshots
- Implement video recording
- Add trace collection
- Configure mobile emulation
Copy-Paste Prompts
Use @browser-automation to automate browser interactions
Phase 5: Visual Regression
Skills to Invoke
playwright-skill- Visual testingui-visual-validator- Visual validation
Actions
- Set up visual testing
- Create baseline images
- Add visual assertions
- Configure thresholds
- Review differences
Copy-Paste Prompts
Use @playwright-skill to implement visual regression testing
Phase 6: Cross-Browser Testing
Skills to Invoke
playwright-skill- Multi-browserwebapp-testing- Browser testing
Actions
- Configure Chromium
- Add Firefox tests
- Add WebKit tests
- Test mobile browsers
- 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 Actionscicd-automation-workflow-automate- CI/CD
Actions
- Create CI workflow
- Configure parallel execution
- Set up artifacts
- Add reporting
- 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 workflowdevelopment- Developmentweb-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
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.
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.
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.
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.
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.
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.