UI-464: Avatar Component Style Extraction #402
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔍 Visual review for your branch is published 🔍Here are the links to: |
GhitaNektt
approved these changes
Sep 11, 2024
GhitaNektt
added
✅ Reviewed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JIRA Ticket
UI-464
QA Steps
1. Navigate to Storybook: Ensure the component is properly set up and viewable in the Storybook environment.
2. Check for Visual Regressions: Thoroughly examine the component's visual appearance and behavior to identify any regressions or unexpected changes compared to the expected state.
3. Verify Right-to-Left (RTL) Layout: Test the component's layout and functionality when rendered in a right-to-left direction to ensure it adapts and functions correctly.
4. Verify Responsiveness: Test the component's layout and behavior across different screen sizes and devices to ensure it adapts and functions correctly.
5. Inspect Class Names: Ensure the component's CSS class names are specific and follow the project's naming conventions to maintain code maintainability and consistency.
6. Perform Build Checks: Build the application and check for any errors or warnings to catch any issues that may prevent successful deployment.
Note
Leave empty when you have nothing to say