The new feature, Virtual Device Testing for Android is here! It is currently in private-beta test phase, please ping us if you want to join! One test can be ran in one build at the moment, and robo test type has some limitations of watching the screenshots and the activity-map. Let’s see an exampl…

Hi @koral , are you saying that behind the scene, Virtual Device Testing step actually calls Firebase Test Lab? Regardless, I believe I’m very close to achieving my goals, please help me a just a bit more koral and @tamaspapik :smiley: Within the life span of Virtual Device Testing step, how can I …

[image] eric-grab: behind the scene, Virtual Device Testing step actually calls Firebase Test Lab Exactly: The tests run on Firebase Test Lab and we display the results we get from them. Source: [image] Device testing for Android With Bitrise’s Android virtual device testing s…

[image] koral: Introducing solid and snappy Virtual Device Testing for Android Thanks @koral Reading main.go and Firebase Test Lab documentation, it’s unclear to me whether you guys are calling a REST API (not found in their documentation) or Gcloud CLI (doesn’t seem to support custom Gradle…

Firebase REST API doesn’t support stuff like that, we have our own server to handle requests, so this is why you won’t see our calls in the official documentation :slight_smile: Thanks @koral ! So basically VDT uses an “offline” solution to test, which means that it prepares/uploads all stuff requir…

Checkout https://github.com/TestArmada/flank for a custom FTL runner that works on bitrise. Spoon is not FTL compatible.

[image] sah: This is great. Been struggling with the Create Emulator, Start Emulator, etc. until I noticed this step. Glad to hear that! :slightly_smiling_face: [image] sah: Is it supported to generate jacoco report from the instrumental tests? Does your jacoco report is generated to …

Thanks for replying. Here’s my current settings: Environment Variables: coverage=true coverageFile=/sdcard/coverage.instrumentaltests Directories to pull: /sdcard And I can see the coverage file downloaded, found and uploaded by the codecov script. But in codecov.io the coverage on the relevan…

If you’re using android test orchestrator, there’s a known bug that breaks coverage generation. Otherwise it should work. Make sure your build.gradle is configured correctly for jacoco coverage and using the latest versions.

After some further investigation I found that codecov can’t process the coverage.ec generated by instrument tests. When I turn it into an xml report, codecov can update the coverage correctly. But instrument tests only seems to generate the .ec file, not the .em, so I can’t convert with ‘emma repor…

How to run Android UI tests on virtual devices

How To Android

sah January 25, 2018, 10:11pm 40

This is great. Been struggling with the Create Emulator, Start Emulator, etc. until I noticed this step.

Is it supported to generate jacoco report from the instrumental tests?

Report coverage Android vitual device testing

Topic		Replies	Views
Report coverage Android vitual device testing Steps step , android	1	1279	October 3, 2019
Collect code coverage during virtual Android device testing Steps android , codecov	14	4067	March 19, 2021
How-to run Android tests on Firebase TestLab Android android , emulator , firebase , how-to	16	10307	September 15, 2021
Run Instrumentation tests on Firebase Physical devices Steps android	0	644	August 22, 2019
Virtual Device Testing for Android - option to override --access-token-file Steps	0	467	April 12, 2022

How to run Android UI tests on virtual devices

Related topics