[GRADLE-1065] Optionally allow for printing test failure stack traces to the console Created: 28/Jul/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Chris Beams Assignee: Unassigned
Resolution: Won't Fix Votes: 2


 Description   

It is currently a hassle to track down a test failure by navigating to the test result HTML. Ideally, a user would be able to supply an option at the command line that causes test failure stack traces to be printed to the console.

This feature should be optional, not on by default. In conjunction with GRADLE-1064, this would form a nice use case:

  1. User runs gradle test
  2. One test fails
  3. User re-runs just that test (see GRADLE-1064), with the test-stack-trace-to-console option enabled
  4. User conveniently identifies problem, fixes problem in code
  5. User re-runs test using GRADLE-1064 support and sees it is fixed.

 Comments   
Comment by Merlyn Albery-Speyer [ 10/Jan/11 ]

+1 for this. How does anyone use Spock power asserts in conjunction with Gradle without something like this?

Comment by Adam Murdoch [ 05/Aug/12 ]

@Chris, can we close this now, given the test logging improvements in Gradle 1.1?

You can skip step 3, as you get the stack trace by default on the console.

Comment by Chris Beams [ 08/Aug/12 ]

Hi Adam,

I've been testing out 1.1 functionality on spring-framework today, and I get results like this during test failures now:

org.springframework.jmx.export.LazyInitMBeanTests > testInvokeOnLazyInitBean FAILED
    org.springframework.beans.factory.BeanCreationException at LazyInitMBeanTests.java:39
        Caused by: java.lang.NoClassDefFoundError at LazyInitMBeanTests.java:39

That is certainly much better than the previous situation, as it tells me which test class and test method failed. However, as you can see the cause is a NoClassDefFoundError, and the name of class that could not be found has been truncated. This isn't too terrible, because at least I know exactly where to go in Eclipse to re-run the test and get the complete stack trace. Worth mentioning, though, at least. Is there a way to turn on even more test output verbosity at the command line?

By the way, making the path to the HTML test results a proper file:// URL is a nice help. I can command-click it from within iTerm now

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 11:46:00 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.