frontend-testing

This skill enables Claude to generate high-quality, comprehensive frontend tests for the Dify project following established conventions and best practices. ⚠️ Authoritative Source : This skill is derived from web/docs/test.md . Use Vitest mock/timer APIs ( vi.* ). Apply this skill when the user: Do NOT apply when: NEVER generate all test files at once. For complex components or multi-file directories: Process in this order for multi-file testing: 📖 See references/workflow.md for complete workflow details and todo list format. When assigned to test a directory/path, test ALL content within that path: Prefer integration testing when writing tests for a directory: See Test Structure Template for correct import/mock patterns. When a component or hook uses useQueryState / useQueryStates : Every test should clearly separate: Each test verifies ONE user-observable behavior: Use should when : For each test file generated, aim for: Note : For multi-file directories, process one file at a time with full coverage each. See references/workflow.md . For more detailed information, refer to: - Asks to write tests for a component, hook, or utility - Asks to review existing tests for completeness - Mentions Vitest , React Testing Library , RTL , or spec files - Requests test coverage improvement - Uses pnpm analyze-component output as context - Mentions testing , unit tests , or integration...