View Android Emulator on the plugin site for more information.
Lets you automatically generate and run an Android emulator for the duration of a build, with the emulator logs being captured as artifacts.
In order to provide effective test coverage of the ever-increasing range of Android platform versions, screen resolutions, densities (amongst other device properties), automated and scalable build tools like Hudson 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 the user's control.
A copy of the Android SDK must be available on each Hudson node you wish to test on.
If you only wish to run pre-existing emulator instances (aka Android Virtual Devices, or AVDs), there are no further requirements — only the basic SDK tools are required.
If you want the plugin to automatically generate new emulator instances, you must install one or more Android platform versions into the SDK.
By default, the SDK only comes with the basic tools; you have to separately download each individual platform version you wish to build or test against.
This is done via the "Android SDK and AVD Manager" tool, accessible via the command line "
android", or via the "Window" menu in Eclipse, if you use the Eclipse ADT plugin. From the SDK Manager, you can easily install the desired "SDK Packages".
On the Hudson master, you can optionally specify the location where each build node can locate a copy of the Android SDK.
This can either be an absolute path, or can contain environment variables in the format
VARIABLE_NAME. This will be replaced at build time from the node's environment variables (see the "Node Properties" settings for each slave), or from the build's environment.
If no value is entered, or the plugin cannot find a valid SDK under the configured path, it will search under the following environment variables on the build node to try and locate a usable SDK:
If you have build slaves running headless, it is recommended to take advantage of Hudson's Xvnc Plugin.
With this plugin enabled, you can run any number of Android emulators in parallel on a headless slave. The Android Emulator plugin has been designed to ensure it always runs after an Xvnc server has been started.
In addition, while the Android Emulator plugin requires the Port Allocator Plugin, there is no job configuration required for this; everything is handled automatically.
Selecting an emulator
After ticking "Run an Android emulator during build", you will be asked whether you want to run an existing AVD, or whether you want to create a new one on-the-fly with certain properties.
Using an existing emulator for a job just requires that you enter the name of the AVD you want to be started. This AVD must exist on each build node the job will be executed on. Existing AVDs are found in your
$HOME/.android/avd directory and can be listed using the "
android list avd" command.
As with all other properties, you can enter environment variables here using the format
Alternatively, if you don't have a particular AVD accessible on each build node, the plugin can automatically generate a new emulator if one doesn't already exist:
The properties should be self-explanatory. Each one is mandatory, aside from the device locale. If this is not entered, the Android emulator default locale of US English (en_US) will be used when starting the emulator.
Each field will auto-complete with the default Android SDK values, i.e 120, 160, 240dpi densities and the six named screen resolutions: QVGA, WQVGA, FWQVGA, HVGA, WVGA, FWVGA. However, you can enter your own values if you wish to use a custom OS image, screen density, resolution or locale.
Screen resolutions can be entered either using the named values, or as a "width times height" dimension, e.g.
Multi-configuration (matrix) job
The real awesomeness of this plugin comes when used in conjunction with a multi-configuration job type.
By using the "Run emulator with properties" setting, in conjunction with one-or-more matrix axes and the Android Emulator plugin's variable expansion, you can generate and test with a large number of distinct Android emulator configurations with very little effort.
To give a full example, if you want to test your application across multiple Android OS versions, multiple screen densities, multiple screen resolutions and for several target locales, you might set up your matrix axes as follows:
As each of these axis names (i.e. "density", "locale", "os", "resolution") are exported by Hudson as environment variables, you can make use of these when launching a new Android emulator:
When the build executes, this would automatically generate and allow you to test your application against 64 unique device configurations.
However, you should note that not all combinations are valid. For example, a QVGA (320x240) resolution device makes no sense with a screen density of 240 (unless you have superhuman eyesight).
For this purpose, you can use the "Combination Filter" feature, which tells Hudson which combinations of the matrix axes are valid. In the case of screen densities and resolutions, a configuration like this should instruct Hudson to only build for configurations which make sense:
Note that each variable refers to one of the matrix axes, not an Android Emulator plugin property.
The full emulator log is captured for the complete duration of a build. This corresponds to the output of "
adb logcat -v time", i.e. the main log output including timestamps.
This will be archived automatically as a build artifact, with the name
For convenience, the plugin places a number of variables into the build environment relating to the emulator in use:
- Coming soon