chore: add anthropic skills for frontend testing

[lyzno1]

Fixes #29609

• chore: init claude skills for frontend testing
• chore: update testing.md
• chore: enhance frontend testing documentation with incremental workflow guidelines and complexity assessment

[gemini-code-assist[bot]]

Summary of Changes

Hello @lyzno1, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly upgrades the frontend testing infrastructure and documentation. It integrates new capabilities for Claude to assist in generating tests according to strict guidelines, ensuring consistency and quality across the Dify project. The changes focus on practical, actionable advice for test authoring, including detailed strategies for mocking, handling asynchronous code, and structuring tests for various component types, all while promoting an incremental, black-box testing approach.

Highlights

• New Frontend Testing Skills for Claude: Introduced a comprehensive set of guidelines and tools to enable Claude to generate high-quality, comprehensive frontend tests for the Dify project, following established conventions and best practices.
• Enhanced Testing Documentation: Updated the core testing.md document and added several new detailed guides covering incremental testing workflows, mocking strategies, async operations, common testing patterns, and domain-specific component testing.
• Test Templates: Provided new test templates for React components, custom hooks, and utility functions to standardize test structure and accelerate test creation.
• Clarified Mocking Rules: Explicitly defined what should and should not be mocked, particularly emphasizing that base components (e.g., Loading, Button) should never be mocked to ensure true integration testing.
• Incremental Testing Workflow: Introduced a critical incremental workflow for testing, especially for multi-file directories, advocating for testing one file at a time and verifying its success before proceeding to the next to simplify debugging and improve test quality.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

[lyzno1]

I have some pull request to test the behavior of Claude Code using the current skills: 1 2 3 4