-
Notifications
You must be signed in to change notification settings - Fork 0
ant tasks
Go to home | documentation
All tasks are devided in several groups:
- General - setup & utility tasks (that didn't fit into other group)
- AVD - create AVD configuration, create and delete AVDs.
- Emulator - start and stop emulator using specified existing AVD.
- Device - number of tasks that are designed to control & communicate with devices (usually through ADB).
Note that device = [emulator|real-device]. In other words, when word device is used, it means that we are talking about both emulators and real-devices.
Note that AVD and emulator are also very related. Under emulator you should understand a live running emulated device. While AVD means a collection of files that are used to run the emulator. In other words there might be several live emulators that are using files from same AVD image.
All tasks are using shared context. This context is created and set up by rbm-setup task. By default this context is saved in a reference with some special name (say rbm-context). All tasks can retrieve context using this default reference name, no action is required from user side.
If user needs to have several contexts he or she might use custom reference name when calling rbm-setup task. User may later specify contextref attribute in any task so that correct context is retrieved.
The shared context also contains device serial number. It's used only by tasks in device group. All other tasks ignore this field.
All device tasks can either retrieve device serial number from context or user may specify serial number using serial attribute. User can set context's serial number using rbm-lock-device and unset it using rbm-unlock-device tasks.
-
rbm-setup- setting up the context to be used by other tasks. -
rbm-restart-adb- restart the adb server, can be used to workaround some issues with emulators.
-
rbm-avd-config- create avd configuration that can later be used to create actual avd. -
rbm-create-avd- create avd using custom arguments or any existing avd configuration. -
rbm-delete-avd- delete avd.
-
rbm-start-emulator- start emulator. -
rbm-stop-emulator- stop emulator. -
rbm-stop-all-emulators- stop all currently running emulators.
-
rbm-lock-device- lock specific device, it will become default and you won't need to specify serial number on other device tasks. -
rbm-unlock-device- unlock currently locked device. -
rbm-get-locked-device- get serial number of currently locked device. -
rbm-get-device-property- get specific device property value -
rbm-start-logcat- start logcat -
rbm-stop-logcat- stop logcat -
rbm-get-apk-package- get package name for specific .apk file -
rbm-install-apk- install .apk to device -
rbm-uninstall-apk- uninstall .apk from device -
rbm-adb-push- push file(s) to device -
rbm-adb-pull- pull file(s) from device -
rbm-adb-shell- run any custom command on device -
rbm-run-tests- run tests on device from specified .apk
Go to home | documentation