Fixed
Status Update
No update yet.
Comments
ch...@google.com
be...@google.com
zb...@gmail.com
This is a terrible oversight on our part but unfortunately there is no clean way to revert this API in order to break Guava dependency.
As a result, there will be a breaking public API change in the next release to address this issue. We introduced an ugly wrapper around Guava Optional class, named EspressoOptional which will live under "android.support.test.espresso.util" namespace. Developers that were using the leaked Guava Optional API will need to change their imports and references to use EspressoOptional during the update to the new version.
Sorry for the inconvenience this may cause. We'll make sure to add a note for this in the next release announcement and change-logs.
As a result, there will be a breaking public API change in the next release to address this issue. We introduced an ugly wrapper around Guava Optional class, named EspressoOptional which will live under "android.support.test.espresso.util" namespace. Developers that were using the leaked Guava Optional API will need to change their imports and references to use EspressoOptional during the update to the new version.
Sorry for the inconvenience this may cause. We'll make sure to add a note for this in the next release announcement and change-logs.
zb...@gmail.com
Would this need a CL at the AndroidJUnitRunner level or in the gradle plugin?
be...@google.com
In such case the raw output from AndroidJUnitRunner contains no mention of the test, which seems wrong.
xa...@google.com
Nick, the change required is in the testing library, right?
nk...@google.com
Yes, we should be able to handle this on our end. I will move this to our component for now.
xa...@google.com
thanks!
nk...@google.com
zb...@gmail.com
Any update on this?
be...@google.com
Stephan - can you assign as appropriate?
sl...@google.com
br...@google.com
Any update on this?
nk...@google.com
nk...@google.com
The fix will be available in the next Runner release v1.0.2.
Description
When tests fail to start (for example because of an error in @BeforeClass), gradle gets confused, it only sees missing test results, no stack trace is captured or reported.
Tested with AndroidJUnitRunner.