Install any skill in seconds. Free to start, no credit card required.
Get Started Free →langgenius/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.
Passed 14 of 21 test cases with the skill, and 3 of 21 without it.
and 18 more in the full report
12 fixed3 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are adding new interactive Storybook stories to primitive components inside `packages/dify-ui/src/primitives`. Where should we look for rules regarding Storybook visual testing and validation commands?
| Checked | Without skill | With skill |
|---|---|---|
| Points to packages/dify-ui/docs/testing.md for primitive testing policy. | Missed | Passed |
| Instructs following the owner document's validation commands. | Missed | Passed |
The instructions your model reads when the skill loads.
Read the testing policy for the package that owns the changed tests:
web/: web/docs/test.md owns Web test boundaries, environments, and commands.packages/dify-ui/: packages/dify-ui/docs/testing.md owns primitive test boundaries, environments, Storybook, and commands.This skill adds no parallel policy or check sequence. Follow the selected owner's requirements, including its validation commands. Recommend deleting low-value tests as readily as adding missing behavior coverage, and report the contract verified and any material verification gap.
test cases passed, vs 3 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.