firebase-test-lab | 易学教程

Firebase Test Lab fails when using ProGuard + Dagger

阅读更多关于 Firebase Test Lab fails when using ProGuard + Dagger

问题 Instrumented tests do pass on local emulators and physical devices but fail on Firebase Test Lab, when the following conditions are met: ProGuard is enabled for the debug builds; There are both Dagger and Espresso dependencies. FTL shows different test issues: 1) In case with APIs 26-28 it shows either Instrumentation run failed due to 'java.lang.NoClassDefFoundError' or Instrumentation run failed due to 'Process crashed.' Exception stacktrace looks like this, it's not always shown in

How to detect running in Firebase Test Lab

阅读更多关于 How to detect running in Firebase Test Lab

问题 I've discovered a problem recently with my app's setup in Firebase. We have the pre-launch report configured, which means that the test lab devices are contributing a large number of anonymous sessions to our analytics. Is there any way to detect that a device is running these tests? For example, will isUserAMonkey or isRunningInTestHarness return true for tests in the test lab? This would allow me to adjust the configuration of my analytics/etc if so. 回答1: This is actually mentioned in the

Pre-launch-report failures due to missing methods (in com.google.android.apps.mtaas.crawler-1/base.apk)

阅读更多关于 Pre-launch-report failures due to missing methods (in com.google.android.apps.mtaas.crawler-1/base.apk)

Since recently my app started to contain strange error messages in the pre-launch reports (automatically generated after upload to the Play store). These reports contain exceptions such as the following: Exception java.lang.NoSuchMethodError: No interface method a(Landroid/arch/lifecycle/e;Landroid/arch/lifecycle/b$a;)V in class Landroid/arch/lifecycle/GenericLifecycleObserver; or its super classes (declaration of 'android.arch.lifecycle.GenericLifecycleObserver' appears in /data/app/com.google.android.apps.mtaas.crawler-1/base.apk) android.arch.lifecycle.f$a.a (f.java:326) android.arch

How to write Espresso Tests which are mocking GPS locations and use them in Google Testlab?

阅读更多关于 How to write Espresso Tests which are mocking GPS locations and use them in Google Testlab?

I recorded an espresso test with Espresso Recorder. I want to test some location changes in my app. Currently I'm mocking the location with this code: LocationManager lm = (LocationManager) context.getSystemService(Context.LOCATION_SERVICE); Criteria criteria = new Criteria(); criteria.setAccuracy( Criteria.ACCURACY_FINE ); String mocLocationProvider = LocationManager.GPS_PROVIDER;//lm.getBestProvider( criteria, true ); lm.addTestProvider(mocLocationProvider, false, false, false, false, true, true, true, 0, 5); lm.setTestProviderEnabled(mocLocationProvider, true); Location loc = new Location

How to write Espresso Tests which are mocking GPS locations and use them in Google Testlab?

阅读更多关于 How to write Espresso Tests which are mocking GPS locations and use them in Google Testlab?

问题 I recorded an espresso test with Espresso Recorder. I want to test some location changes in my app. Currently I'm mocking the location with this code: LocationManager lm = (LocationManager) context.getSystemService(Context.LOCATION_SERVICE); Criteria criteria = new Criteria(); criteria.setAccuracy( Criteria.ACCURACY_FINE ); String mocLocationProvider = LocationManager.GPS_PROVIDER;//lm.getBestProvider( criteria, true ); lm.addTestProvider(mocLocationProvider, false, false, false, false, true,