julianharty
commented
7 years ago Some notes: Google provide a simple app that requests permissions at runtime https://github.com/googlesamples/android-RuntimePermissions This may be a useful testbed.
On StackOverflow there's a useful recent discussion on permissions: https://stackoverflow.com/questions/33929937/android-marshmallow-test-permissions-with-espresso/
Google recently released a utility method (in beta) to grant permissions https://developer.android.com/reference/android/support/test/rule/GrantPermissionRule.html It's still new and there are few examples of it being used. Some users on SO report problems using it. I'm hoping it'll enable us to bypass both the "screen overlay detected" (by granting permissions before the tests start) and the need to grant permissions to access the SD card.
Here's a ticket on various ways to disable animations: https://github.com/ardock/android-topeka/issues/1
stale[bot]
kelson42
macgills
There are a couple of challenges when running automated tests on various Android devices. These include:
Each and all of these can cause some of our automated application tests to fail.
We have already implemented some code to try and handle prompts for permissions which reduce the number of devices that are affected. I'd like to further enhance the test scripts so that we can minimise the effects of these aspects of the Android run-times on various devices. Then we can run our automated tests across a wider range of device and operating-system revisions.
This is one of several tasks to improve the reliability, scalability, and trustworthiness of our automated tests.
Notes: Android's Permission model changed significantly in Android M (API 23)
As the docs say:
Espresso's test runner will often complain if it decides that animations are enabled on a device
Google's Android team provided an example of how to disable animations. For instance, here's an example from running the current Espresso Tests on one of my devices
and Google Developers provided a fairly complex script (available from the Internet Archive) to try to disable animations at runtime. However, that doesn't seem ideal, especially as it was intended for much older releases of Android:
Screen Overlays have been a bugbear for users and for automated testing for several years. I'm not aware of a reliable way to set/address this warning for automated tests.
I'd like to find ways to ameleorate or fully address these frustrations. This ticket is to track the individual issues and our progress. We may create additional issues for specific areas and/or changes depending on the detail & depth needed.