Fixed
Status Update
No update yet.
Comments
sl...@google.com
Here's a really detailed StackOverflow answer that seems to point out some things to look at in relation to this behaviour:
http://stackoverflow.com/a/14293528/238753
sl...@google.com
su...@twofortyfouram.com
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
sl...@google.com
Tested and confirmed that this bug affects Android 4.4 - 5.1 but was fixed in Android 6.0.
I've attached an updated sample project since the original one needed some tweaks to get it building.
I've attached an updated sample project since the original one needed some tweaks to get it building.
Description
Version used: 3.0.0-alpha-1
What steps will reproduce the problem?
1. Create a test that requires a physical device
2. Annotate the test with @RequiresDevice
3. Run the test on a virtual device on Firebase Test Lab
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
Build APK ./gradlew assembleDebugAndroidTest then invoking gcloud by the command line.
What is the expected output? What do you see instead?
Expected: the test is skipped.
Actual: The test is executed. Note that this works correctly on an AVD running locally; it just doesn't correctly detect the FTL virtual device as being virtual.
This appears to be a regression in alpha-1.