The Android Emulator, unfortunately, doesn’t work in CircleCI’s conventional (Docker-based) Android build environment. With a little tinkering, though, we can make it work in another environment!
What Doesn’t Work
So if you own Windows, macOS, or Linux computer or laptop then Android 12 Emulator is the best free way to run android apps on a computer via Android Studio software. In this article, we are sharing a detailed guide and tutorial on How to Install and Run Android 12 on PC with Android 12 Emulator integrated into Android Studio software.
Since CircleCI 2.0, the recommended build environment for most projects is the Docker Executor. Overall, it’s great: Docker images are fast, portable, and cacheable. Chances are you can start with a prebuilt one.
One of the jobs in our current workflow boots up the circleci/android:api-29-node image in about four seconds with all the build tools we need. For building and publishing, this is fantastic.
Unfortunately, when you begin configuring your tests, you’ll soon realize that this environment can’t run the Emulator.
Why?
- Click on releases option and download the latest preview version by clicking of android emulator m1 preview.dmg. It will download a DMG file. Click on the DMG file in downloads folder of your Mac.
- Not only this, but it is also a cross-platform emulator and allows access to run all the Android applications from the Windows or macOS. BrowserStack This one allows you to run tests across several devices and desktop browsers to ensure that the software goes far and beyond organizational and customer expectations.
To achieve reasonable performance, the Android Emulator needshardware acceleration, which depends on supporting capabilities from the processor and operating system. We can use the Emulator’s -accel-check flag to interrogate a system’s compatibility. Here’s what it says in a CircleCI Docker environment:
(That means “no.”)
But wait! Docker is but one of several executors available on CircleCI. What if we use a conventional Linux VM instead of Docker? (This is called the machine executor).
That doesn’t work either. Bummer.
At this point, you might heed CircleCI’s advice and pursue a third-party service like Firebase Test Lab or AWS Device Farm, but I wasn’t ready to give up yet.
What Works
We were already using CircleCI’s MacOS support to build and test our React Native app for iOS. I had one last wacky idea to try: could we run the Android Emulator on MacOS?
It works!
Configuration
Without the convenience of an externally-maintained Docker image, it’s on you to install the Android tools. If you want to try Android testing on MacOS, hopefully our configuration can save you some time:
And here’s install-android-tools.sh:
Conclusion
It’s unorthodox, but this approach has worked reasonably well so far for our small React Native project. One set of Appium tests can run against both iOS and Android, and they run the same way in CircleCI that they do locally.
I’d be interested to hear about your experiences with Android UI tests in CircleCI, whether via a third-party service, a CI host that supports the Emulator, or another approach altogether.
The Android Emulator, unfortunately, doesn’t work in CircleCI’s conventional (Docker-based) Android build environment. With a little tinkering, though, we can make it work in another environment!
What Doesn’t Work
Since CircleCI 2.0, the recommended build environment for most projects is the Docker Executor. Overall, it’s great: Docker images are fast, portable, and cacheable. Chances are you can start with a prebuilt one.
One of the jobs in our current workflow boots up the circleci/android:api-29-node image in about four seconds with all the build tools we need. For building and publishing, this is fantastic.
Unfortunately, when you begin configuring your tests, you’ll soon realize that this environment can’t run the Emulator.
Why?
Mac Os Emulator For Windows
To achieve reasonable performance, the Android Emulator needshardware acceleration, which depends on supporting capabilities from the processor and operating system. We can use the Emulator’s -accel-check flag to interrogate a system’s compatibility. Here’s what it says in a CircleCI Docker environment:
(That means “no.”)
But wait! Docker is but one of several executors available on CircleCI. What if we use a conventional Linux VM instead of Docker? (This is called the machine executor).
That doesn’t work either. Bummer.
At this point, you might heed CircleCI’s advice and pursue a third-party service like Firebase Test Lab or AWS Device Farm, but I wasn’t ready to give up yet.
What Works
We were already using CircleCI’s MacOS support to build and test our React Native app for iOS. I had one last wacky idea to try: could we run the Android Emulator on MacOS?
Mac Os X Emulator
It works!
Configuration
Without the convenience of an externally-maintained Docker image, it’s on you to install the Android tools. If you want to try Android testing on MacOS, hopefully our configuration can save you some time:
And here’s install-android-tools.sh:
Conclusion
It’s unorthodox, but this approach has worked reasonably well so far for our small React Native project. One set of Appium tests can run against both iOS and Android, and they run the same way in CircleCI that they do locally.
I’d be interested to hear about your experiences with Android UI tests in CircleCI, whether via a third-party service, a CI host that supports the Emulator, or another approach altogether.