
E2e Testing
This is a solid foundation for Playwright-based E2E testing that pushes you toward the page object model and away from brittle selectors. The selector priority is spot on: data-testid first, then roles and labels, never CSS classes or XPath. The auth state reuse pattern alone will save you minutes on every test run. What I appreciate here is the opinionated structure with clear boundaries: this is for full user workflows across the stack, not component tests or API contracts. The wait strategy section is practical, showing you exactly what to use instead of those shameful `waitForTimeout(3000)` calls we've all written. The examples are Python/React focused but the patterns translate to any stack running Playwright.
- skills.sh installs
- 1.6K
- GitHub stars
- 8
- last updated
- Aug 21, 2026
Install
$ npx -y skills add hieutrtr/ai1-skills --skill e2e-testing --agent claude-codeInstalls into .claude/skills of the current project.
Files
E2E Testing
When to Use
Activate this skill when:
- Writing E2E tests for complete user workflows (login, CRUD operations, multi-page flows)
- Creating critical path regression tests that validate the full stack
- Testing cross-browser compatibility (Chromium, Firefox, WebKit)
- Validating authentication flows end-to-end
- Testing file upload/download workflows
- Writing smoke tests for deployment verification
Do NOT use this skill for:
- React component unit tests (use
react-testing-patterns) - Python backend unit/integration tests (use
pytest-patterns) - TDD workflow enforcement (use
tdd-workflow) - API contract testing without a browser (use
pytest-patternswith httpx)
Instructions
Test Structure
Sponsors
Details
- Repository
- github.com/hieutrtr/ai1-skills
- Categories
- Frontend Development, Backend & APIs, Testing & QA, Documentation, Automation & Workflows, Python