Lets you automatically generate, launch and run interact with an Android emulator for the duration of during a build, with the emulator logs being captured as artifacts.
Table of Contents
|Table of Contents|
Due to a serious bug introduced in SDK Tools r12 (see Android bug #18444), running any builds with the "Use emulator snapshots" option enabled (which is the default), will likely fail to load in the state you expect. For example the emulator may not be ready for use, and the screen may not be unlocked.
Until the above issue is fixed (which is currently targeted for r14), it is recommended to:
If you have already upgraded, you should uncheck "Use emulator snapshots" in any jobs where you are seeing problems.
In order to provide effective test coverage of the ever-increasing range of Android platform versions, screen resolutions and densities (amongst other device properties), automated and scalable build tools like Jenkins become highly advantageous.
This plugin aims to vastly simplify automated testing of Android applications across a wide range of virtual devices by automatically generating emulator instances, starting up those emulators and capturing the logging output, with many device parameters being under your control.
This plugin lets you automate a number of Android-related tasks during a build:
- Creating a new Android emulator
- Its configuration can be parameterised, including OS version, screen size, language and hardware properties
- Running any Android emulator
- Waits until the emulator is fully started-up
- Emulator snapshots can be automatically created
- This allows a very fast startup time for subsequent builds
- This ensures subsequent builds will start from the same clean state
- Logs are automatically captured and saved
- Emulator will be shut down automatically when the build has finished
- Multiple instances of the same emulator are automatically prevented from running concurrently
- Installing an Android package onto an emulator
- Uninstalling an Android package from an emulator
- Running the
- Parsing output from running
- The build outcome can be automatically marked as unstable or failed in case a crash is detected
Jenkins version 1.377 or newer is required.
Since this version was released well before the Hudson/Jenkins split, this plugin can also be used with Hudson. Any changes to this will be posted here and on the Hudson wiki.