Fixed
Status Update
Comments
ch...@google.com <ch...@google.com>
be...@google.com <be...@google.com>
zb...@gmail.com <zb...@gmail.com> #2
The link in the above description doesn't work external to google, expanded link: https://issuetracker.google.com/issues/73450636
zb...@gmail.com <zb...@gmail.com> #3
This will be fixed in the next release.
be...@google.com <be...@google.com> #4
In such case the raw output from AndroidJUnitRunner contains no mention of the test, which seems wrong.
xa...@google.com <xa...@google.com> #5
Nick, the change required is in the testing library, right?
nk...@google.com <nk...@google.com> #6
Yes, we should be able to handle this on our end. I will move this to our component for now.
xa...@google.com <xa...@google.com> #7
thanks!
nk...@google.com <nk...@google.com>
zb...@gmail.com <zb...@gmail.com> #8
Any update on this?
be...@google.com <be...@google.com> #9
Stephan - can you assign as appropriate?
sl...@google.com <sl...@google.com>
br...@google.com <br...@google.com> #10
Any update on this?
nk...@google.com <nk...@google.com>
nk...@google.com <nk...@google.com> #11
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.