Fixed
Status Update
No update yet.
Comments
fr...@gmail.com
This is a regression in the test support library 1.0 / Espresso 3.0.0. The issue does not occur if using the previous version of the testing support library 0.5, Espresso 2.2.2 or Espresso 2.3-alpha
fr...@gmail.com
The ClassNotFoundException is being reported because the class could not be loaded because its base class could not be found. That behavior is correct if the class name has been explicitly specified. However, if the class name was obtained by scanning the path (which I assume is what is happening in this case) then it should ignore class loading errors.
Can you confirm that the test from step 2 is actually run even though a test failure is being reported for the unloadable class?
Can you confirm that the test from step 2 is actually run even though a test failure is being reported for the unloadable class?
Description
getResultData returns the ActivityResult of an activity that has finished.
ActivityResultMatcher provides matchers to verify the resultCode and the resultData of the activityResult.
Possible implementation is published here:
The matchers should go into package android.support.test.espresso.contrib;
Use case:
The user clicks on a button of an activity A that picks a content item, then the activity returns this item as the activity result usually in onActivityResult of the parent activity P.
To simplify testing the activity result should be tested within the test of activity A