…nce this should be instrumented using the ShadowProvider interface (including play servcies shadows on classpath) Existing tests that relied on having this package instrumented (e.g: for allowing mocks of final classes) can use the following configuration in their test runner temporarily as they shouldn't be relying on this behaviour. return InstrumentationConfiguration.newBuilder() .addInstrumentedPackage("com.google.android.gms") .build();
Since da0b674 which introduced a ShadowVelocityTracker, shadowing the GestureDetector has become mostly unnecessary. Now, the shadow executes actual code, which makes the class behave as expected. Change-Id: Ifbfa8d49e02b40fd57260e387f6889188b488305
With the new animation realism, infinite animations keep on, well, just running infinitely, blocking test execution. For testing purposes, the shadow sets the repeat count to 1 for such animations, but you can still obtain the actual set count from the shadow.
It's possible that the code under test modifies intents in a different thread than main, causing the comparator to crash to an NPE at various points. Change-Id: Ic1876ae685b1ef010f5d497dd776bb576d46a67b