fec-e2e-testing
Installation
SKILL.md
E2E Test Specification
Purpose
Validate key user journeys with real browsers and uncover integration risks not covered by unit tests.
Procedure
- 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.
- 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.
- Use Page Object or fixtures to encapsulate login, page locator and shared data, and avoid naked selectors in the spec.
- Assert that the user can see the results, relying on Locator automatic waiting, network response or visible status, without using fixed sleep.
- CI must upload HTML report, screenshots, trace or video; Flaky use cases must be isolated, reproduced, marked with sources and associated with issues.
- When debugging fails, read the trace, console, network and screenshots first, and then change the test; do not misjudge real product defects as flaky.
- Record the test environment, seed data and cleanup strategies for key browser capabilities, payment, permissions, uploads and real-time communication processes.
- Test data must be repeatable: API seeds, database fixtures, test accounts or mock services are preferred; random data must have a unique prefix and be cleaned in teardown.