summaryrefslogtreecommitdiff
path: root/platform/android/TESTS.md
diff options
context:
space:
mode:
authorPablo Guardiola <guardiola31337@gmail.com>2017-03-30 23:23:44 +0200
committerGitHub <noreply@github.com>2017-03-30 23:23:44 +0200
commit1a0dc66486f3bf2236fd308b502e9edacd30ec54 (patch)
tree6e15b85fddde019b98cbd3b836445731e0a3abf3 /platform/android/TESTS.md
parent003caddbc0ad3bf9f7cf189996733d552977d5da (diff)
downloadqtlocation-mapboxgl-1a0dc66486f3bf2236fd308b502e9edacd30ec54.tar.gz
update test documentation adding how to run firebase tests within android studio (#8566)
Diffstat (limited to 'platform/android/TESTS.md')
-rw-r--r--platform/android/TESTS.md117
1 files changed, 117 insertions, 0 deletions
diff --git a/platform/android/TESTS.md b/platform/android/TESTS.md
new file mode 100644
index 0000000000..f0bdeb2dce
--- /dev/null
+++ b/platform/android/TESTS.md
@@ -0,0 +1,117 @@
+# Mapbox GL Test App
+
+## Testing
+
+### Running Espresso tests on a device
+
+This test project comes with all the required Android Testing Support Library dependencies
+in the Gradle file. Tests are under the `app/src/androidTest` folder.
+
+Note that before running your tests, you might want to turn off animations on your test device.
+It's a known issue that leaving system animations turned on in a test device
+(window animation scale, transition animation scale, animator duration scale)
+might cause unexpected results, or may lead tests to fail.
+
+To create a new run configuration:
+* Click on Run -> Edit Configurations...
+* Click on the plus sign and then on "Android Tests"
+* Give a name to the configuration, e.g. `TestAppTests`
+* Choose the `MapboxGLAndroidSDKTestApp` module
+* Choose `android.support.test.runner.AndroidJUnitRunner` as the instrumentation runner
+* Click OK to save the new configuration
+
+You can now run this configuration from the main toolbar dropdown menu.
+
+### Running Espresso tests on Firebase within AS
+
+Tests are under the `app/src/androidTest` folder.
+
+1) _Sign In_ with your Google account.
+
+![Firebase Tests AS 1][1]
+
+2) Or _Add Account_ if you want to sign in with a different account.
+
+![Firebase Tests AS 2][2]
+
+3) Select the test configuration you want to run and click _Play_ button.
+
+4) Click on _Cloud Testing_ tab. You need to create a project in Firebase and define a _Matrix configuration_ previously (see
+[Firebase Test Lab for Android guide](https://firebase.google.com/docs/test-lab/overview)). Select your template (e.g. _Nexus 5 (3)_).
+
+5) Select your _Cloud project_ (e.g. _android-gl-native (android-gl-native)_).
+
+![Firebase Tests AS 3-5][3]
+
+6) Click on _OK_ button to run the tests.
+
+![Firebase Tests AS 6][4]
+
+7) When tests finish the results will appear within AS.
+
+![Firebase Tests AS 7][5]
+
+### Running Espresso tests on AWS Device Farm
+
+On a terminal, within `mapbox-gl-native/android/java`,
+run the tests (`cC` stands for `connectedCheck`):
+
+```
+$ ./gradlew -Pmapbox.abis=all cC -p MapboxGLAndroidSDKTestApp
+```
+
+Then:
+* Go to your AWS Console and choose Device Farm.
+* Create a new project, e.g. `MapboxGLAndroidSDKTestApp`
+* On step 1, upload the APK in `mapbox-gl-native/android/java/MapboxGLAndroidSDKTestApp/build/outputs/apk/MapboxGLAndroidSDKTestApp-debug-unaligned.apk`
+* On step 2, choose Instrumentation, test filter is `com.mapbox.mapboxgl.testapp.MainActivityTest` and upload the APK in `mapbox-gl-native/android/java/MapboxGLAndroidSDKTestApp/build/outputs/apk/MapboxGLAndroidSDKTestApp-debug-androidTest-unaligned.apk`
+* On step 3, choose a device pool. E.g. Top Devices
+* On step 4, customize your device state (if needed)
+* Finally, confirm the configuration and run the tests.
+
+On Step 2, you can also separate by commas different classes: `com.mapbox.mapboxgl.testapp.MainActivityTest,com.mapbox.mapboxgl.testapp.MainActivityScreenTest`
+
+If you have no tests for your app, or want to test some random user behavior,
+you can just choose "Built-in: Fuzz" in step 2.
+
+### Running pure JUnit tests
+
+These tests run on a local JVM on your development machine and they are extremely fast to run
+(as compared to Espresso). These tests are located under `src/test/java`. To run them you switch
+to the Unit Tests build variant, then right click the corresponding test class or method
+and select "Run ...".
+
+You can also have a run configuration:
+* Click on Run -> Edit Configurations...
+* Click on "Junit Tests"
+* Give a name to the configuration, e.g. `JUnit tests`
+* As "Test Kind", choose "All in directory"
+* As folder, choose the following folder: `mapbox-gl-native/android/java/MapboxGLAndroidSDKTestApp/src/test/java`
+* Click OK to save the new configuration
+
+You can also run the tests from the command line with:
+
+```
+$ ./gradlew -Pmapbox.abis=none test -p MapboxGLAndroidSDKTestApp
+```
+
+### Running the UI/Application Exerciser Monkey
+
+Similar to the "Built-in: Fuzz" test mentioned above, Android provides
+[Monkey](http://developer.android.com/tools/help/monkey.html),
+"a program that runs on your emulator or device and generates pseudo-random streams of user events
+such as clicks, touches, or gestures, as well as a number of system-level events."
+
+To exercise Monkey on the test app, install the package on the device (e.g. via Android Studio)
+and then:
+
+```
+$ adb shell monkey -p com.mapbox.mapboxgl.testapp -v 500
+```
+
+
+[1]: ./art/tests/FirebaseTestsAS_1.png
+[2]: ./art/tests/FirebaseTestsAS_2.png
+[3]: ./art/tests/FirebaseTestsAS_3-5.png
+[4]: ./art/tests/FirebaseTestsAS_6.png
+[5]: ./art/tests/FirebaseTestsAS_7.png