Use Gradle-managed devices for tests #56
Draft
Conversation
This file contains hidden or 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
![google-labs-jules[bot]](https://avatars.githubusercontent.com/in/842251?s=80&v=4){kind=small}
This commit configures the project to use Gradle-managed devices for running Android instrumented tests. This automates the creation and management of emulators, simplifying the testing process for both local development and CI. The following changes were made: - Added a `testOptions.managedDevices` block to `sample/build.gradle.kts` to define four Gradle-managed devices. - Device names are dynamically generated based on the API levels from the version catalog. - `pixel2Api*` devices for local testing. - `atdApi*` (AOSP-ATD) devices for CI. - Created two device groups, `localDevices` and `ciDevices`, to run tests on multiple devices in parallel. - Updated the `update.sh` script to use the `localDevicesDebugAndroidTest` task. - Simplified the GitHub Actions workflow in `.github/workflows/build.yml` by removing the manual emulator setup and running the tests on the `ciDevices` group.
This commit configures the project to use Gradle-managed devices for running Android instrumented tests. This automates the creation and management of emulators, simplifying the testing process for both local development and CI. The following changes were made: - Added a `testOptions.managedDevices` block to `sample/build.gradle.kts` to define four Gradle-managed devices using the non-deprecated `localDevices` container. - Device names are now dynamically generated based on the API levels from the version catalog. - `pixel2Api*` devices for local testing. - `atdApi*` (AOSP-ATD) devices for CI. - Created two device groups, `localDevices` and `ciDevices`, to run tests on multiple devices in parallel. - Updated the `update.sh` script to use the `localDevicesDebugAndroidTest` task. - Simplified the GitHub Actions workflow in `.github/workflows/build.yml` by removing the manual emulator setup and running the tests on the `ciDevices` group.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll acknowledge your comments with a 👀 emoji and then get to work. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! I will automatically address your feedback on specific files or sections of files. For any comments you don't want me to act on, just include PS: Responding to comments on the entire PR are not yet supported but coming soon. For security, I will only act on instructions from the user who triggered this task for this pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This change migrates the project to use Gradle-managed devices for running instrumented tests, which automates emulator management for both local and CI environments. It also configures device groups to run tests in parallel, with device names dynamically generated from version catalog properties.