
Frontend Testing
This generates Vitest and React Testing Library tests for Dify's frontend codebase, following their conventions around file placement, mocking patterns, and integration-first testing. It's built from their internal test.md docs, so it knows to put tests in sibling __tests__ directories, use real project components instead of mocking everything, and handle nuqs query state testing with the right adapters. The workflow is deliberately incremental: one file at a time, run it, fix it, then move on. Useful when you're adding coverage to a feature directory or need tests that match existing patterns. It won't help with E2E or Python tests, just the web layer unit and integration work.
- skills.sh installs
- 3.8K
- GitHub stars
- 160.8K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add langgenius/dify --skill frontend-testing --agent claude-codeInstalls into .claude/skills of the current project.
Files
Frontend Testing
Read the testing policy for the package that owns the changed tests:
web/:web/docs/test.mdowns Web test boundaries, environments, and commands.packages/dify-ui/:packages/dify-ui/docs/testing.mdowns 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.
Sponsors
Details
- Repository
- github.com/langgenius/dify
- Categories
- Frontend Development, Testing & QA, Git & Pull Requests, Documentation, Code Review & Quality, Python