Run Android UI tests on virtual devices. This Step collects the built APK/AAB file from the $BITRISE_APK_PATH and in case of instrumentation tests, the $BITRISE_TEST_APK_PATH Environment Variables and uses Firebase Test Lab to run UI tests on them.
The available test types are instrumentation, robo, gameloop.
You can read our detailed guide about using the Step with other Bitrise Steps. Here we'll go over the configuration options of the Step.
Make sure the App path input points to the path of the APK or AAB file of your app. If you use our Android Build or Android Build for UI Testing Steps, you don't need to change the default value.
Add the devices you want the tests to run on in the Test devices input.
You need to set the device ID, the version, the orientation, and the language. Read the input description for more information and available devices.
Choose a test type.
The available options are:
For detailed configuration options related to the different test types, please check out the full guide.
You can also export the results of the Step to the Test reports add-on. All you need to do is to add a Deploy to Bitrise.io Step to the end of your Workflow.
If you get the Build already exists error, it is because you have more than one instance of the Step in your Workflow. This doesn't work as Bitrise sends the build slug to Firebase and having the Step more than once in the same Workflow results in sending the same build slug multiple times.
