test: add comprehensive frontend tests for billing plan assets

[lyzno1]

Summary

This PR adds comprehensive frontend tests for the billing/plan/assets components using the Claude Code frontend-testing skill.

Changes

• Add unit tests for Sandbox, Professional, Team, and Enterprise icon components
• Add integration tests for the assets barrel export (index.tsx)
• Achieve 100% code coverage across all files (362/362 statements, 4/4 branches, 4/4 functions)
• 98 test cases covering:
  • Component rendering and SVG structure
  • Accessibility patterns
  • Edge cases and error handling
  • Real-world usage scenarios
  • Performance and memoization

Test Coverage

All files in billing/plan/assets directory:

• Statements: 100% (362/362)
• Branches: 100% (4/4)
• Functions: 100% (4/4)
• Lines: 100% (362/362)

Test Execution

All tests pass successfully:

• 5 test suites
• 98 test cases
• 100% coverage

Generated With

Tests generated using Claude Code frontend-testing skill following Dify testing conventions and best practices.

[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 enhances the frontend testing infrastructure by introducing a comprehensive suite of tests for the billing plan assets and establishing a robust set of documentation and templates for future testing efforts. The changes ensure critical UI components are thoroughly validated and standardize the testing process across the project, promoting higher code quality and maintainability.

Highlights

• Comprehensive Frontend Tests: Added extensive frontend tests for the billing plan assets, including unit tests for individual icon components (Enterprise, Professional, Sandbox, Team) and integration tests for their barrel export.
• 100% Code Coverage: Achieved 100% code coverage across all newly tested files, with 98 test cases covering rendering, accessibility, edge cases, and performance.
• New Frontend Testing Documentation: Introduced a new .claude/skills/frontend-testing directory containing detailed guides and templates for frontend testing, covering async operations, common patterns, domain-specific components, mocking strategies, and an incremental testing workflow.
• Updated Testing Guidelines: Modified web/testing/testing.md to incorporate new best practices, such as black-box assertions, explicit instructions against mocking base components, and a comprehensive path-level testing strategy for directories.
• Tooling Alignment: Updated internal configuration files (.cursorrules, .github/copilot-instructions.md, .windsurf/rules/testing.md) to reference the new canonical frontend testing documentation.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/autofix.yml

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]