They both look the same in workflow editor

[rakibhasanbd4723]

Verification instrumentation/robo workflow

Here we use Virtual device testing preceded by Gradle runner step to build an app (APKs or AABs). The latter differs from the Gradle Unit Test by additionally exporting paths to bulgaria mobile number output artifacts needed in tests. Finally, we use Deploy to Bitrise.io step so we can see VDT results (including video and screenshots). Note that we don’t use such a step in verification workflow since Danger takes care of publishing the most of the results (lint and detect warnings) and the rest can be easily retrieved from the build log.

Deploy workflows
In most Android app projects there at least 2 deployable variants: connected with non-prod environment used for internal testing (usually called QA or staging) and another one connected with production for public releases. Even if there are more environments they often can be divided into 2 groups: non-public and public and workflows for any flavor belonging to the given group will look similar.

Staging version
Deploy staging workflow

In this example, we’ll deploy the app using Firebase App Distribution. Note that at the time of writing that service is still in beta stage but it replaced deprecated Fabric Beta. If you are using another distribution platform e.g. AppCenter or TestFairy look at the Bitrise Integrations list, there might be ready steps for them. Note that in the case of Android projects some services provides also dedicated Gradle plugins, so you may configure everything in buildscript instead of using additional steps.