[GRADLE-3556] Mocked exception type can cause unexpected behavior in the junit test runner Created: 13/Sep/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Lari Hotari Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Issue Links:
Related
Related to GRADLE-2759 Test execution infrastructure errors ... Resolved

 Description   

Reported on the forums:
The test was attempting to mock a complex exception type (using Mockito). This exception was wrapped and rethrown by the method under test. It appears as if gradle encountered an error because there was no stack trace on the mocked exception.

https://discuss.gradle.org/t/gradle-test-runner-does-not-mark-junit-test-case-as-failed-if-exception-is-encountered-missing-stack-trace/19482

test app:
https://github.com/clarkstuth/gradle-failure-scenario

 Comments   
Comment by Lari Hotari [ 13/Sep/16 ]

Related reports on forum:
https://discuss.gradle.org/t/messageioexception-could-not-read-message-from/14680
https://discuss.gradle.org/t/added-new-test-now-npe-during-test-task/9070

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:51:53 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.