End-to-end testing user flows using browser automation
Scanned 10/6/2026
Skills Directorynpx -y skills add DongDuong2001/pudo-code-system --skill e2e --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of E2e?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dongduong2001-e2e)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: e2e-test
description: End-to-end testing user flows using browser automation
---
# End-to-End (E2E) Test Skill
This skill handles full-stack browser and user-journey automation testing.
## When to use this skill
- When verifying critical business flows (e.g., User Signup, Checkout, Payment).
- When using tools like Playwright, Cypress, or Selenium.
- When testing the actual deployed frontend against a real environment.
## Guidelines
- **High ROI Flows:** Only E2E test the most critical user journeys. These tests are slow and brittle.
- **Resilient Selectors:** Prefer querying elements by testing-specific data attributes (e.g., `data-testid`) or ARIA roles rather than fragile CSS classes.
- **Avoid Sleep:** Never use hardcoded wait/sleep times. Wait for specific network requests to complete or elements to become visible/interactive.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
