Absolutely, this is totally feasible! Here's how you can pull this off for your UI tests that rely on Gmail and Google Play access:

1. Start with the right system image #

First, you need to use an Android emulator image that includes Google Mobile Services (GMS) — regular Android system images don’t have Google Play or the Google Account framework. When creating your AVD (Android Virtual Device), pick a Google Play or Google APIs system image for your target API level (e.g., Android 13 (API 33) Google Play Intel x86 Atom_64 System Image). This is non-negotiable, since you can’t log into a Google account without GMS.

2. Save a pre-configured snapshot (easiest approach for CI) #

This is the most reliable way to preserve your logged-in state:

• Launch your AVD manually, go through the initial setup, and log into your dedicated test Google account. Verify that Gmail and Google Play are fully signed in and working as expected.
• When closing the emulator, select the Save snapshot option. This captures the entire device state, including your logged-in Google account.
• In your Jenkins pipeline, start the emulator with this pre-saved snapshot using the command:

  emulator -avd <your-avd-name> -no-boot-anim -load-snapshot <your-snapshot-name> -accel on
  

  The -accel on flag enables hardware acceleration, which is critical for keeping emulator performance snappy in CI environments.

3. Automate account setup with scripts (for dynamic environments) #

If snapshots aren’t flexible enough (e.g., you need to switch accounts per test), you can automate the login flow using ADB and UI automation tools:

• First, ensure your test Google account has two-step verification disabled (or use an app-specific password if 2FA is required) — this avoids manual auth prompts that break CI.
• After launching the emulator, wait for it to fully boot with:

  adb wait-for-device shell 'while [[ -z $(getprop sys.boot_completed) ]]; do sleep 1; done'
  

• Use tools like UIAutomator (or basic adb input commands, though less reliable) to simulate navigating to the Google Account settings, entering your credentials, and completing the login flow. UIAutomator is preferable because it’s resilient to small UI changes.

4. CI-specific considerations for Jenkins #

• Resource allocation: Emulators are resource-hungry. Make sure your Jenkins runner has at least 2 CPU cores and 4GB of memory allocated. Hardware acceleration is a must — without it, your tests will run painfully slow or fail entirely.
• Cache AVD assets: To avoid rebuilding the AVD every time, cache the ~/.android/avd/ directory in Jenkins. This saves time by reusing your pre-configured AVD and snapshot across pipeline runs.
• Validate account state before tests: Occasionally, Google might sign you out due to security checks. Add a pre-test step to verify the account is logged in — for example, query Gmail's content provider to check for an active account:

  adb shell content query --uri content://com.google.android.gm/messages --projection account_name
  

  If no account is returned, re-run your login automation script.

With these steps, you’ll have a Jenkins-ready emulator that boots up with your Google account already configured, ready to run UI tests that depend on Gmail and Google Play access.

内容的提问来源于stack exchange，提问作者Mina Wissa