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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

Repository: langgenius/dify
Path: .agents/skills/frontend-testing/SKILL.md
Commit: 02f0e8c

Last updated: about 9 hours ago
First committed: 7 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.