e2e-testing
End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.
Best use case
e2e-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.
Teams using e2e-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/e2e-testing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How e2e-testing Compares
| Feature / Agent | e2e-testing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
wordpress-penetration-testing
This skill should be used when the user asks to "pentest WordPress sites", "scan WordPress for vulnerabilities", "enumerate WordPress users, themes, or plugins", "exploit WordPress vu...
elixir-testing
Elixir testing patterns: ExUnit, Mox behaviour-based mocking, StreamData property testing, Phoenix integration tests. Use when writing tests for Elixir/Phoenix applications.
web-security-testing
Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.
ssh-penetration-testing
This skill should be used when the user asks to "pentest SSH services", "enumerate SSH configurations", "brute force SSH credentials", "exploit SSH vulnerabilities", "perform SSH tu...
sqlmap-database-pentesting
This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns...
sql-injection-testing
This skill should be used when the user asks to "test for SQL injection vulnerabilities", "perform SQLi attacks", "bypass authentication using SQL injection", "extract database inform...
smtp-penetration-testing
This skill should be used when the user asks to "perform SMTP penetration testing", "enumerate email users", "test for open mail relays", "grab SMTP banners", "brute force email cre...
idor-testing
This skill should be used when the user asks to "test for insecure direct object references," "find IDOR vulnerabilities," "exploit broken access control," "enumerate user IDs or obje...
html-injection-testing
This skill should be used when the user asks to "test for HTML injection", "inject HTML into web pages", "perform HTML injection attacks", "deface web applications", or "test conten...
cloud-penetration-testing
This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfiguratio...
burp-suite-testing
This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp ...
aws-penetration-testing
This skill should be used when the user asks to "pentest AWS", "test AWS security", "enumerate IAM", "exploit cloud infrastructure", "AWS privilege escalation", "S3 bucket testing...