| name | frontend-testing |
| description | Use when writing or changing Vitest or React Testing Library tests under `web/` or `packages/dify-ui/`, or when the user explicitly requests frontend test strategy, including evaluation of an existing strategy. Do not use for frontend code-review-only requests, general testability discussion, Python tests, or Cucumber/Playwright E2E. |
Frontend Testing
web/docs/test.md is the single policy owner. Read it before changing frontend tests; this skill adds no separate requirements.
- Identify the observable contract and regression risk.
- Choose the smallest boundary that includes the behavior owner.
- Establish the failing case first when practical, then implement one coherent scenario.
- Run the focused spec before the affected suite and relevant static checks.
- Report the behavior verified and any remaining browser, visual, or end-to-end risk.
Recommend deleting low-value tests as readily as adding missing behavior coverage. Use web/docs/test.md for policy and Web commands; use the packages/dify-ui/README.md Development section for Dify UI commands.
