Skip to content

Conversation

@tagboola
Copy link
Contributor

@tagboola tagboola commented Oct 27, 2025

Description

Add a tool for getting available devices for testing and update prompt to use the tool.

Screenshot 2025-10-27 at 3 47 28 PM Screenshot 2025-10-27 at 3 38 50 PM

Scenarios Tested

Sample Commands

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @tagboola, 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 introduces a foundational utility to programmatically fetch a list of available devices for app testing. This enhancement to the apptesting module provides a structured and API-driven method to query device availability, which is intended to be integrated into future prompts for device selection, streamlining the testing workflow.

Highlights

  • New Tool Added: A new tool named get_devices has been introduced within the apptesting module. This tool is designed to retrieve a list of available devices for automated testing.
  • Google Testing API Integration: The get_devices tool leverages the google.testing('v1') API to fetch test environment catalogs, requiring an OAuth token for authentication.
  • Tool Availability: The newly created get_devices tool has been added to the apptestingTools array, making it accessible as a server tool for use in the system.
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
Contributor

@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

The pull request introduces a new tool, get_devices, for retrieving available devices for testing. This tool is added to the apptestingTools array. The get_devices tool uses the Google Cloud Testing API to fetch device information based on the specified device type (e.g., ANDROID).

Comment on lines +17 to +24
async ({ type }) => {
const testing = google.testing("v1");
return toContent(
await testing.testEnvironmentCatalog.get({
oauth_token: await getAccessToken(),
environmentType: type,
}),
);
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The oauth_token parameter is deprecated. Consider using the auth parameter instead, which automatically handles authentication using the service account or user credentials. This simplifies the code and avoids potential issues with token management.

// Example using auth parameter
await testing.testEnvironmentCatalog.get({
  auth: await google.auth.getClient({ scopes: ['https://www.googleapis.com/auth/cloud-platform'] }),
  environmentType: type,
});
    const testing = google.testing("v1");
    return toContent(
      await testing.testEnvironmentCatalog.get({
        auth: await google.auth.getClient({ scopes: ['https://www.googleapis.com/auth/cloud-platform'] }),
        environmentType: type,
      }),
    );

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmm, oauth_token does not seem to be deprecated 🤔

image

}),
},
async ({ type }) => {
const testing = google.testing("v1");
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe call this testingClient or gtestClient?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

@tagboola tagboola changed the title Add get devices tool Add support for selecting devices when running automated tests Oct 27, 2025
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.

2 participants