dify icon indicating copy to clipboard operation
dify copied to clipboard

test: try to use Anthropic Skills to add tests for web/app/components/apps/

Open lyzno1 opened this issue 2 months ago • 2 comments

  • chore: init claude skills for frontend testing
  • chore: update testing.md
  • chore: enhance frontend testing documentation with incremental workflow guidelines and complexity assessment
  • test: add comprehensive tests for web/app/components/apps/

lyzno1 avatar Dec 13 '25 05:12 lyzno1

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 establishes a robust framework for frontend testing by integrating Anthropic Skills, providing extensive documentation, and implementing a set of initial tests for key application components. The changes aim to standardize testing methodologies, promote an incremental testing workflow, and ensure higher quality and maintainability of the frontend codebase.

Highlights

  • Anthropic Skills Integration: Introduced new Anthropic Skills specifically designed to assist with frontend test generation and review, aiming to standardize and improve testing practices.
  • Enhanced Testing Documentation: Significantly updated and expanded frontend testing documentation, including detailed checklists, workflow guides (incremental approach, async testing, common patterns, domain-specific components), and comprehensive test templates for React components, hooks, and utilities.
  • Comprehensive Frontend Tests: Added a suite of new, comprehensive tests for components within the web/app/components/apps/ directory, covering AppCard, Empty, Footer, List, NewAppCard, and custom hooks like useAppsQueryState and useDSLDragDrop.
  • Updated Testing Principles: Modified core testing principles to explicitly emphasize black-box assertions, preferring role-based queries and pattern matching, and strictly prohibiting the mocking of base components to ensure true integration testing.
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.

gemini-code-assist[bot] avatar Dec 13 '25 05:12 gemini-code-assist[bot]

Please do not merge

lyzno1 avatar Dec 13 '25 06:12 lyzno1