e2e-test

Generate Playwright end-to-end tests in an isolated git worktree.

1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/WhatIfWeDigDeeper/application-tracker --skill e2e-test-whatifwedigdeeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/WhatIfWeDigDeeper/application-tracker/tree/main/.claude/skills/e2e-test
Command: npx skills add https://github.com/WhatIfWeDigDeeper/application-tracker --skill e2e-test-whatifwedigdeeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of comprehensive end-to-end tests for web application features, ensuring robust and reliable software.

Core Features & Use Cases

  • Automated Test Generation: Creates Playwright tests for specified features or patterns.
  • Isolated Worktree: Uses git worktrees to ensure a clean testing environment.
  • Use Case: Quickly generate e2e tests for a new user authentication flow or a complex dashboard component.

Quick Start

Use the e2e-test skill to create Playwright tests for the login-form feature.

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I generate Playwright e2e tests for specific application features?

You can generate Playwright e2e tests by specifying feature names, glob patterns, or all features. The tool creates tests covering happy paths, edge cases, and accessibility using data-testid selectors.

How does git worktree isolation work for end-to-end test generation?

Git worktree isolation creates a clean testing environment by generating Playwright e2e tests within an isolated git worktree. This ensures that automated test generation does not interfere with your main working directory.

Can I use glob patterns to create Playwright tests for multiple features at once?

Yes, Playwright test generation supports glob patterns to target multiple application features simultaneously. This allows you to create comprehensive test suites covering happy paths, edge cases, and accessibility.

Do I need data-testid selectors to automate e2e testing for web applications?

Using data-testid selectors is required for the generated Playwright e2e tests. This ensures robust and reliable test targeting for happy paths, edge cases, and accessibility checks across your web application features.

What is the best way to automate end-to-end test suite creation for a new user authentication flow?

Automating end-to-end test suite creation for a user authentication flow involves generating Playwright tests within an isolated git worktree. This approach ensures comprehensive coverage of happy paths, edge cases, and accessibility.

Does e2e testing cover accessibility checks or just happy paths?

E2e testing covers both happy paths and accessibility checks, along with edge cases. Generated Playwright tests ensure comprehensive coverage for robust web application features using data-testid selectors.