test(web): add unit tests for Avatar component
Closes #30200
Added comprehensive tests for the Avatar component covering:
- Rendering with image URL vs fallback initial
- Size, className, and textClassName props
- Image load error handling and state recovery
- Edge cases like empty names, CJK characters, zero/large sizes
All tests pass locally. Should help catch regressions when touching this component.
Summary of Changes
Hello @SherlockShemol, 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 stability of the Avatar component by introducing a comprehensive suite of unit tests. These tests validate the component's rendering logic, prop handling, image loading error recovery, and behavior under various edge conditions, aiming to prevent future regressions and ensure consistent functionality.
Highlights
- Comprehensive Unit Tests: Added a new test file (
index.spec.tsx) to provide extensive unit test coverage for theAvatarcomponent, ensuring its reliability and preventing regressions. - Rendering Scenarios: Tests now cover how the Avatar component renders with a valid image URL versus falling back to an initial character when no image is provided.
- Prop Validation: Validated the correct application of
size,className, andtextClassNameprops, ensuring they modify the component's appearance as expected in various scenarios. - Image Error Handling: Implemented tests for image load error handling, including scenarios where an image fails to load, how the component recovers, and how the error state is managed upon prop changes.
- Edge Case Coverage: Addressed various edge cases such as empty names, names containing CJK characters, empty string avatars, and extreme
sizevalues (zero or very large) to ensure robust behavior.
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.
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.