bitmask_android issueshttps://0xacab.org/leap/bitmask_android/-/issues2018-10-07T11:05:25Zhttps://0xacab.org/leap/bitmask_android/-/issues/8749automate tests for different android versions and devices2018-10-07T11:05:25Zaguestuserautomate tests for different android versions and devices# Motivation:
Enable LEAP to build APK's with confidence that they will work on the most widely distributed Android devices and OS versions, given a passing test suite.
# Acceptance Criteria:
When code is checked in, automated test su...# Motivation:
Enable LEAP to build APK's with confidence that they will work on the most widely distributed Android devices and OS versions, given a passing test suite.
# Acceptance Criteria:
When code is checked in, automated test suite is run inside a docker container against:
* Bank of emulators with fixed device (Samsung Galaxy) and varying API version (16 - 25).
* Bank of emulators with fixed API version (23) and varying devices (Galaxy, Nexus, Pixel, ...)
# Reasoning:
* Samsung Galaxy is the most widely used Android Device
* API v 23 (Lollipop) is the most widely installed Android OS
# Questions:
* API versions 16-18 (Jellybean) account for only 10% of Android users (vs: 20% for Kitkat, 32% for Lollipop 1&2, 31% for Marshmallow, & 5% for Nougat). Should we support it?
* What devices should we test against? How much value do we get from varying devices?
* I would like to investigate our Google Developer Console to see what the distribution of devices and API versions is among our current userbase. Can I (@aguestuser) have access to do that?
# Resources:
* [Distribution of different Android Platforms](https://developer.android.com/about/dashboards/index.html#Platform)
* [Distribution of different Android Devices](http://www.appbrain.com/stats/top-android-phones)
* [Distribution of different Android Manufacturers](http://www.appbrain.com/stats/top-manufacturers)cybertacyberta