e2e-setup — Claude Code command: what it does, how to install
Sets up end-to-end testing in your project, selects a framework like Playwright or Cypress, and prepares CI integration.
npx claude-code-templates@latest --command testing/e2e-setupWhat e2e-setup does
The command inspects your repository with Bash. It looks for files like index.html or App.tsx and checks package.json for React or Vue. It also checks for existing test suites and CI workflow files.
Based on the detected context or passed arguments (--playwright, --cypress, --puppeteer, --webdriver, --mobile), the command builds the test environment. It installs dependencies, sets up Page Object patterns, and configures test data fixtures.
Execution depends on Bash and file editing permissions; without shell access, auto-detection fails immediately. The command then hooks execution into your CI pipeline for automated runs.
What it helps with
- configure an E2E testing framework matched to the stack
- scaffold a project structure with Page Object patterns
- organize test fixtures and database cleanup routines
- integrate automated test execution into CI/CD pipelines
Example prompts for the agent
- /e2e-setup --playwright
- Set up end-to-end testing for this project using /e2e-setup --cypress
- /e2e-setup --mobile
How to install e2e-setup
1claude-code-templates
npx claude-code-templates@latest --command testing/e2e-setup2Manually: put the files in place
.claude/commands/e2e-setup.mdCall it with /e2e-setup. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/e2e-setup.mdCall it with /prompts:e2e-setup. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/e2e-setup.prompt.mdManually: put the files in place
.gemini/commands/e2e-setup.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about e2e-setup
How to install e2e-setup in Claude Code?
Run npx claude-code-templates@latest --command testing/e2e-setup in your terminal or save the command template at .claude/commands/e2e-setup.md.
What does e2e-setup do?
It inspects your project files, installs an E2E framework, creates Page Object templates, and connects test runs to CI/CD.
Which frameworks does e2e-setup support?
It supports Cypress, Playwright, WebDriver, Puppeteer, and mobile setups, or it can auto-detect the best fit from existing project files.
Source text
e2e-setup.md · MIT
--- allowed-tools: Read, Write, Edit, Bash argument-hint: "[framework] | --cypress | --playwright | --webdriver | --puppeteer | --mobile" description: Configure comprehensive end-to-end testing suite with framework selection and CI integration --- # E2E Setup Configure comprehensive end-to-end testing suite with framework optimization: **$ARGUMENTS** ## Current E2E Context - Application type: !`find . -name "index.html" -o -name "app.js" -o -name "App.tsx" | head -1 && echo "Web app" || echo "Detect app type"` - Framework: !`grep -l "react\\|vue\\|angular" package.json 2>/dev/null || echo "Detect framework"` - Existing tests: !`find . -name "cypress" -o -name "playwright" -o -name "e2e" | head -1 || echo "No E2E setup"` - CI system: !`find . -name ".github" -o -name ".gitlab-ci.yml" | head -1 || echo "No CI detected"` ## Task Implement comprehensive end-to-end testing with framework selection and optimization: **Framework Focus**: Use $ARGUMENTS to specify Cypress, Playwright, WebDriver, Puppeteer, mobile testing, or auto-detect best fit **E2E Testing Framework**: 1. **Framework Selection & Setup** - Choose optimal E2E tool, install dependencies, configure basic settings, setup project structure 2. **Test Environment Configuration** - Setup test environments, configure base URLs, implement environment switching, optimize test isolation 3. **Page Object Patterns** - Design page object model, create reusable components, implement element selectors, optimize maintainability 4. **Test Data Management** - Setup test data strategies, implement fixtures, configure database seeding, design cleanup procedures 5. **Cross-Browser Testing** - Configure multi-browser execution, setup mobile testing, implement responsive testing, optimize compatibility 6. **CI/CD Integration** - Configure automated execution, setup parallel testing, implement reporting, optimize performance **Advanced Features**: Visual regression testing, accessibility testing, performance monitoring, API testing integration, mobile device testing. **Quality Assurance**: Test reliability optimization, flaky test prevention, execution speed optimization, debugging capabilities. **Output**: Complete E2E testing setup with framework configuration, test suites, CI integration, and maintenance workflows.
© davila7 · MIT · davila7/claude-code-templates