Add custom auto-enablement for app testing

[tagboola]

Description

By default, tools and prompts for products are enabled by the following process:

• If the product is defined in the firebase.json file
• If the API has been enabled and can be reached for the project

Because out product won't necessarily be defined in the firebase.json, I added a custom enablement function that enables our tools/prompts if:

• The app is a mobile app and
• Our API has been enabled and can be reached for the project

Scenarios Tested

Sample Commands

[gemini-code-assist]

Summary of Changes

Hello @tagboola, I'm Gemini Code Assist¹! 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 specialized auto-enablement process for Firebase App Testing features. It moves away from the standard firebase.json based configuration for this product, instead enabling App Testing tools and prompts dynamically if the project is identified as a mobile application (Android, iOS, or Flutter) and the necessary API is active. This change streamlines the developer experience for mobile projects by making App Testing readily available without manual configuration.

Highlights

• Custom Auto-Enablement for App Testing: Introduced a custom mechanism to automatically enable App Testing tools and prompts. Unlike other products that rely on firebase.json configuration, App Testing will now be enabled if the project is detected as a mobile application (Android, iOS, or Flutter) and its corresponding API is active.
• New Availability Logic: Added a new utility function isAppTestingAvailable which determines the availability of App Testing by checking if the project directory contains mobile app structures (e.g., Android, iOS, Flutter files) and if the App Distribution API is enabled for the project.
• Feature Registration: The 'apptesting' feature has been added to the list of DETECTED_API_FEATURES and its custom availability check (isAppTestingAvailable) has been registered in the system, overriding the default firebase.json based enablement.
• Tool and Prompt Updates: Existing prompt and tool definitions for App Testing (specifically runTest, run_tests, and check_test) have been updated to explicitly declare 'apptesting' as their associated product.
• Unit Tests for Availability: Comprehensive unit tests have been added for the isAppTestingAvailable function, covering various scenarios including non-mobile projects, disabled APIs, and different types of mobile projects (Android, iOS, Flutter) with enabled APIs.

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

[gemini-code-assist]

Code Review

This pull request adds a custom auto-enablement check for the App Testing feature, which is a great addition. The implementation correctly verifies if the project is a mobile app and if the necessary API is enabled. The new logic is well-integrated into the existing prompt and tool framework. I've provided a few suggestions to improve the code, including removing a describe.only from a test file which is important to fix, cleaning up some commented-out code, and a minor refactoring for better readability.