Skip to content

fix: use correct test tag in BookmarksScreen LoadingState#2089

Open
ishaquehassan wants to merge 1 commit intoandroid:mainfrom
ishaquehassan:fix/2086-bookmarks-loading-test-tag
Open

fix: use correct test tag in BookmarksScreen LoadingState#2089
ishaquehassan wants to merge 1 commit intoandroid:mainfrom
ishaquehassan:fix/2086-bookmarks-loading-test-tag

Conversation

@ishaquehassan
Copy link

The LoadingState composable in BookmarksScreen.kt was using .testTag(forYou:loading), which is a copy-paste from ForYouScreen. This causes UI tests checking for the bookmarks loading state to match the wrong screen. Changed to .testTag(bookmarks:loading) to follow the naming convention used elsewhere in the same file: bookmarks:feed and bookmarks:empty. Fixes #2086

@ishaquehassan ishaquehassan requested a review from dturner as a code owner March 10, 2026 13:19
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 addresses a UI testing issue by correcting an incorrectly applied test tag within the Bookmarks screen's loading state. The change ensures that UI tests targeting the bookmarks loading state will correctly identify the intended component, aligning with the established naming conventions for the screen.

Highlights

  • Test Tag Correction: The LoadingState composable in BookmarksScreen.kt was updated to use the correct test tag bookmarks:loading instead of forYou:loading.

🧠 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.

Changelog
  • feature/bookmarks/impl/src/main/kotlin/com/google/samples/apps/nowinandroid/feature/bookmarks/impl/BookmarksScreen.kt
    • Updated the test tag for the LoadingState composable from forYou:loading to bookmarks:loading.
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 👍 and 👎 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.

Footnotes

  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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly updates the testTag for the LoadingState composable in BookmarksScreen.kt from forYou:loading to bookmarks:loading, resolving a UI test issue and aligning with established naming conventions. No security vulnerabilities were found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: BookmarksScreen loading state uses incorrect test tag

2 participants