Files

Stephen Niedzielski 9747caa435 Fix Android ProGuard View rules & release signing

- Enable ProGuard for the test app so the most common use case may be tested.
- Update ProGuard to keep all Mapbox views and their methods.
  Previously, ProGuard was stripping numerous class methods including
  UserLocationView.g/setAccuracy(). These particular methods are
  accessed via reflection. On newer APIs, this manifests only in Logcat
  and loss of functionality:

   PropertyValuesHolder  W  Method setAccuracy() with type float not found on target class class com.mapbox.mapboxsdk.views.UserLocationView
                         W  Method getAccuracy() with type null not found on target class class com.mapbox.mapboxsdk.views.UserLocationView

  On Android 4.03 and 4.04 (API 15), this causes an NPE:

    java.lang.NullPointerException
      at android.animation.PropertyValuesHolder.setupSetterAndGetter(PropertyValuesHolder.java:513)
      at android.animation.ObjectAnimator.initAnimation(ObjectAnimator.java:385)
      at android.animation.ValueAnimator.setCurrentPlayTime(ValueAnimator.java:537)
      at android.animation.ValueAnimator.start(ValueAnimator.java:927)
      at android.animation.ValueAnimator.start(ValueAnimator.java:950)
      at android.animation.ObjectAnimator.start(ObjectAnimator.java:363)
      at com.mapbox.mapboxsdk.views.UserLocationView.setLocation(UserLocationView.java:401)
      at com.mapbox.mapboxsdk.views.UserLocationView.toggleGps(UserLocationView.java:300)
      at com.mapbox.mapboxsdk.views.UserLocationView.setEnabled(UserLocationView.java:230)
      at com.mapbox.mapboxsdk.views.MapView.setMyLocationEnabled(MapView.java:3122)
      ...

  Also add Support libraries rules to the test. Further amendments may
  be made by examining usage.txt[0,1].

[0] http://developer.android.com/tools/help/proguard.html#enabling
[1] http://proguard.sourceforge.net/manual/usage.html#shrinkingoptions

2015-12-10 20:47:11 -08:00

src

[android] #3224 - add espresso test for TiltActivity

2015-12-09 14:54:38 -08:00

build.gradle

Fix Android ProGuard View rules & release signing

2015-12-10 20:47:11 -08:00

lint.xml

[android] Move android files

2015-10-25 01:07:16 +11:00

proguard-rules.pro

Fix Android ProGuard View rules & release signing

2015-12-10 20:47:11 -08:00

README.md

[android] Move android files

2015-10-25 01:07:16 +11:00

README.md

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 AWS Device Farm

On a terminal, within mapbox-gl-native/android/java, run the tests (cC stands for connectedCheck):

$ ./gradlew 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 behaviour, 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 test --continue -p MapboxGLAndroidSDKTestApp

Running the UI/Application Exerciser Monkey

Similar to the "Built-in: Fuzz" test mentioned above, Android provides Monkey, "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