Individual skill
fec-e2e-testing
Use when creating, maintaining, debugging, or reviewing real-browser end-to-end tests with Playwright or Cypress, including Page Object models, CI artifacts, traces, flaky tests, cross-page visual regression, and critical user journeys such as login, payment, permissions, or CRUD. For layer planning or tests close to UI components, choose the matching testing workflow first; Chinese triggers include E2E, end-to-end testing, Playwright, Cypress.
skills/fec-e2e-testing/SKILL.md
Source commit 5d44782572025045a552ff8945b354726eb5d183
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 23
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- claude-code-skills Repository topic
- e2e-tests Repository topic
- fronend-development Repository topic
- frontend-plugin Repository topic
- frontend-project Repository topic
- react Repository topic
- typescript Repository topic
- vue3 Repository topic
- testing Derived category
- design Derived category
- operations Derived category
- testing-browser Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,522 bytesreferences/e2e-ci-reporting.mddoc · 1,470 bytesreferences/e2e-special-scenarios.mddoc · 1,869 bytesreferences/e2e-visual-regression.mddoc · 2,208 bytesreferences/playwright-patterns.mddoc · 2,301 bytes
Read excerpt
# E2E Test Specification
## Purpose
Validate key user journeys with real browsers and uncover integration risks not covered by unit tests.
## Procedure
1. Clarify the key journeys: cross-page processes such as login, purchase, creation, search, permissions, payment, etc. are given priority; if you only choose the test level, do the test hierarchical planning first.
2. New projects will be given priority by Playwright; existing Cypress projects will continue to use Cypress and will not be migrated for the sake of migration.
3. Use Page Object or fixtures to encapsulate login, page locator and shared data, and avoid naked selectors in the spec.
4. Assert that the user can see the results, relying on Locator automatic waiting, network response or visible status, without using fixed sleep.
5. CI must upload HTML report, screenshots, trace or video; Flaky use cases must be isolated, reproduced, marked with sources and associated with issues.
6. When debugging fails, read the trace, console, network and screenshots first, and then change the test; do not misjudge real product defects as flaky.