CODEWITHSUNDEEP
androiddockerandroid-emulatorcontinuous-integration
ElyashivLavi
ElyashivLavi

Reputation: 1811

Run AndroidTest on Android Emulator In Docker

I saw some links and posts about running AndroidTest in Docker. Like:

https://dzone.com/articles/running-android-tests-in-docker

https://github.com/ksoichiro/android-tests/tree/master/docker-emulator

And some more. However, they all seem inappropriate for AndroidTest in CI, since they require an actual VM, or simply they are too old.

I tried the following lines Docker Image (Partial):

RUN /opt/adk/tools/bin/sdkmanager "emulator" "build-tools;${BUILD_TOOLS}" "platforms;${ANDROID_PLATFORM}" "system-images;${ANDROID_PLATFORM};google_apis;armeabi-v7a" \
    && echo no | /opt/adk/tools/bin/avdmanager create avd -n "Android" -k "system-images;${ANDROID_PLATFORM};google_apis;armeabi-v7a" \

And then I run the emulator using:

/opt/adk/emulator/emulator @Android -writable-system -nocache -no-snapstorage &

However, when trying to run connectedAndroidTest there were some weird exceptions, like: Caused by: com.android.ddmlib.InstallException: Unknown failure: Error: Could not access the Package Manager. Is the system running?

Or, if I try to manually install the test APK, and run am instrument: android.util.AndroidException: Can't connect to activity manager; is the system running?

So my question: Is anyone is running AndroidTest on emulator as part of the CI on docker? Means, an image that you just need to mount your project and run gradle connectedAndroidTest, and everything works? Is there a working example for that?

Upvotes: 4

Views: 4214

Answers (1)

Christian Hofer
Christian Hofer

Reputation: 11

I run AndroidTest on emulator as part of the CI on docker using this image: https://hub.docker.com/r/chrisss404/android-emulator

The problem you might encounter is that hardware acceleration is not available on your host because of missing nested KVM (just a guess, but that was the problem I was facing). In this case you have to use software rendering, which can take a significant amount of time.

With software rendering, the startup takes about 40 minutes until the emulator is usable (on my host). However, then you can run the instrumentation tests as usual in an acceptable timeframe.

Upvotes: 1

Related Questions