Split unit and functional tests in Firebase Performance Gradle plugin

[tejasd]

Splits the tests in the Firebase Performance Gradle plugin into unit tests and functional tests.

The functionalTest target is added to the :deviceCheck target to ensure that it's run as part of the instrumentationTest CI runs.

Also updates the .github/workflows/perf-gradle-compatibility-tests.yml to run the new target.

[gemini-code-assist]

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

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.

[github-actions]

📝 PRs merging into main branch

Our main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released.

[tejasd]

Verified locally w/

• ./gradlew :firebase-perf-gradle:deviceCheck withErrorProne --rerun-tasks
• ./gradlew :firebase-perf-gradle:check withErrorProne --rerun-tasks