E2e Testing Automation

This helps Claude write E2E tests that actually simulate user behavior across your full stack. You get working examples for Playwright, Cypress, and Selenium with proper patterns like Page Object Model, stable selectors using data-testid attributes, and explicit waits instead of sleeps. Use it when you need to test critical flows like checkout or signup, validate multi-step workflows, or catch regressions from UI changes. The practical advice on what not to do is honestly more valuable than most E2E guides: skip brittle selectors, don't share state between tests, and stop trying to E2E test every edge case when unit tests would work fine.

skills.sh installs: 695
GitHub stars: 379
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aj-geddes/useful-ai-prompts --skill e2e-testing-automation --agent claude-code

Installs into .claude/skills of the current project.

Files

Overview

End-to-end (E2E) testing validates complete user workflows from the UI through all backend systems, ensuring the entire application stack works together correctly from a user's perspective. E2E tests simulate real user interactions with browsers, handling authentication, navigation, form submissions, and validating results.

When to Use

Testing critical user journeys (signup, checkout, login)
Validating multi-step workflows
Testing across different browsers and devices
Regression testing for UI changes
Verifying frontend-backend integration
Testing with real user interactions (clicks, typing, scrolling)
Smoke testing deployments

Quick Start

Minimal working example:

// tests/e2e/checkout.spec.ts
import { test, expect, Page } from "@playwright/test";

test.describe("E-commerce Checkout Flow", () => {
  let page: Page;

  test.beforeEach(async ({ page: p }) => {
    page = p;
    await page.goto("/");
  });

SKILL.md on GitHub