frontend-testing
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.
Install
npx skillscat add langgenius/dify/frontend-testing Install via the SkillsCat registry.
Here's a thinking process: 1. **Analyze the Request:** - I need to write a 2-3 sentence plain-text summary in English. - It must objectively explain: - What this skill does - What problem it solves - When an agent or developer should use it - Constraints: - Objective, factual tone only: no marketing language, no superlatives, no calls to action - Natural prose, no bullet points, no headings, no markdown formatting - Do not wrap the answer in quotes - At most 60 words - Output: ONLY the summary text. 2.
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 packages/dify-ui/docs/testing.md for Dify UI commands.
Categories
Install
npx skillscat add langgenius/dify/frontend-testing Install via the SkillsCat registry.
Repository Stars
The star count shown is for the parent repository (langgenius/dify), not this specific skill.
.agents/skills/frontend-testing