MR
Mayur Rathi
@mayurrathi
⭐ 40.7k GitHub stars

E2E Testing

E2E Testing is an productivity AI skill with a core value of End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration. It helps developers solve real-world problems in the productivity domain, boosting efficiency, automating repetitive tasks, and optimizing workflows.

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

Last verified on: 2026-07-07

Quick Facts

Category productivity
Works With Claude
Source sickn33/antigravity-awesome-skills
Stars ⭐ 40.7k
Last Verified 2026-07-07
Risk Level High
mkdir -p ./skills/e2e-testing && curl -sfL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/e2e-testing/SKILL.md -o ./skills/e2e-testing/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# 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

text 
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

text 
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

text 
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

text 
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

text 
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

text 
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

text 
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

🎯 Best For

  • QA engineers
  • Developers writing unit tests
  • Claude users
  • Knowledge workers
  • Remote teams

💡 Use Cases

  • Generating test cases for edge conditions
  • Writing integration test suites
  • Using E2E Testing in daily workflow
  • Automating repetitive productivity tasks

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply E2E Testing to Your Work

    Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.

  4. 4

    Review and Refine

    Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.

❓ Frequently Asked Questions

Does this generate test mocks?

Many testing skills include mock generation. Check the install command and skill content for details.

How do I install E2E Testing?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/e2e-testing/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Not testing edge cases

AI tends to generate happy-path tests. Manually review for boundary conditions.

Not reading the full skill

Skills contain important context and edge cases beyond the quick start.

🔗 Related Skills

circleci-automation Circleci Automationodoo-automated-tests odoo-automated-teststdd-workflow Tdd Workflowacceptance-orchestrator acceptance-orchestratorapify-competitor-intelligence apify-competitor-intelligenceapify-influencer-discovery apify-influencer-discovery