E2e Testing Automation
aj-geddes/useful-ai-promptsEnd-to-end (E2E) tests check that the whole application works from a user's point of view. They simulate real user interactions like clicking buttons, typing text, and navigating pages. These tests cover the full application stack from the front end through to the back end systems.
Developers and testers use E2E tests to make sure important tasks like signing up or checking out work without problems. The tests run on different browsers and devices to catch issues before users see them. This helps keep the app reliable and easy to use.
With tools like Playwright, Cypress, and Selenium, you can build test scripts that run automatically. The best practice is to focus on critical user journeys and use stable selectors like data-testid attributes. Automated E2E testing saves time and prevents bugs from reaching production.
Add E2e Testing Automation skill to your workflow
Global
mkdir -p ~/.claude/skills/e2e-testing-automationProject
mkdir -p .claude/skills/e2e-testing-automationSource Repository
More Testing & QA Claude Code Skills
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step