chore: import upstream snapshot with attribution
This commit is contained in:
@@ -0,0 +1,44 @@
|
||||
---
|
||||
name: e2e-testing-patterns
|
||||
description: "Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do."
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
---
|
||||
|
||||
# E2E Testing Patterns
|
||||
|
||||
Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.
|
||||
|
||||
## Use this skill when
|
||||
|
||||
- Implementing end-to-end test automation
|
||||
- Debugging flaky or unreliable tests
|
||||
- Testing critical user workflows
|
||||
- Setting up CI/CD test pipelines
|
||||
- Testing across multiple browsers
|
||||
- Validating accessibility requirements
|
||||
- Testing responsive designs
|
||||
- Establishing E2E testing standards
|
||||
|
||||
## Do not use this skill when
|
||||
|
||||
- You only need unit or integration tests
|
||||
- The environment cannot support stable UI automation
|
||||
- You cannot provision safe test accounts or data
|
||||
|
||||
## Instructions
|
||||
|
||||
1. Identify critical user journeys and success criteria.
|
||||
2. Build stable selectors and test data strategies.
|
||||
3. Implement tests with retries, tracing, and isolation.
|
||||
4. Run in CI with parallelization and artifact capture.
|
||||
|
||||
## Safety
|
||||
|
||||
- Avoid running destructive tests against production.
|
||||
- Use dedicated test data and scrub sensitive output.
|
||||
|
||||
## Resources
|
||||
|
||||
- `resources/implementation-playbook.md` for detailed E2E patterns and templates.
|
||||
Reference in New Issue
Block a user