fec-component-testing
Installation
SKILL.md
#Component testing
Purpose
Use tests close to the code and user behavior to verify pure logic, component contracts, and lightweight module collaboration to reduce refactoring and UI interaction regression.
Procedure
1. First determine the test level
- Unit testing: pure functions, hooks/composables, utils, state logic, schema.
- Component testing: props/emis, callbacks, user interaction, loading/error/empty, mock boundaries.
- Lightweight integration testing: form + API mock + Router/Store/Provider context.
The cross-page real browser process is offloaded to the E2E workflow; if the test layer selection is unclear, do the test layering planning first.
2. Prioritize testing based on user-perceivable behavior
Each test keeps Arrange / Act / Assert clearly segmented: preparing data and rendering, performing user actions, asserting user-visible results or exposing contracts.