Agent skill · software engineering · aj-geddes
e2e-testing-automation
Build end-to-end automated tests that simulate real user interactions across the full application stack. Use for E2E test, Selenium, Cypress, Playwright, browser automation, and user journey testing.
Why this skill is useful
Provides specific automation scripts and best practices for E2E testing with tools like Playwright and Cypress that the AI wouldn't reliably generate on its own.
What it needs
Requires cypress, playwright, selenium installed locally. About 2k tokens when loaded. Last updated 2026-03-04. 307 stars on the source repository.
What this skill does
E2E Testing Automation Table of Contents Overview When to Use Quick Start Reference Guides Best Practices 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: Reference Guides Detailed implementations in the references/ directory: Guide Contents --- --- Playwright E2E Tests Playwright E2E Tests Cypress E2E Tests Cypress E2E Tests Selenium with Python (pytest) Selenium with Python (pytest) Page Object Model Pattern Page Object Model Pattern Best Practices ✅ DO Use data-testid attributes for stable selectors Implement Page Object Model for maintainability Test critical user journeys thoroughly Run tests in multiple browsers (cross-browser testing) Use explicit waits instead of sleep/timeouts Clean up test data after each test Take screenshots on failures Parallelize test execution where possible ❌ DON'T Use brittle CSS selectors (like nth-child) Test every possible UI combination (focus on critical paths) Share state between tests Use fixed delays (sleep/timeout) Ignore flaky tests Run E2E tests for unit-level testing Test third-party UI components in detail Skip mobile/responsive testing
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/e2e-testing-automation