Android Instrumented Test
![Step changelog](https://shields.io/github/v/release/bitrise-steplib/bitrise-step-android-instrumented-test?include_prereleases&label=changelog&color=blueviolet)
Runs Instrumented tests on an existing APK
Description
Runs Instrumented tests on an existing APK
🧩 Get started
Add this step directly to your workflow in the Bitrise Workflow Editor.
You can also run this step directly with Bitrise CLI.
⚙️ Configuration
Inputs
Key |
Description |
Flags |
Default |
main_apk_path |
The path to the app's main APK |
required |
$BITRISE_APK_PATH |
test_apk_path |
The path to the app's test APK |
required |
$BITRISE_TEST_APK_PATH |
test_runner_class |
The name of the test runner |
required |
androidx.test.runner.AndroidJUnitRunner |
additional_testing_options |
A space-delimited list of additional options to pass to the test runner Example: If a value of KEY1 true KEY2 false is passed to this input, then it will be passed to the adb command like so: shell adb shell am instrument -e "KEY1" "true" "KEY2" "false" [...] See the adb documentation for more info. |
|
|
Outputs
There are no outputs defined in this step
🙋 Contributing
We welcome pull requests and issues against this repository.
For pull requests, work on your changes in a forked repository and use the Bitrise CLI to run step tests locally.
Learn more about developing steps: