[GRADLE-1388] Report time elapsed by unit tests Created: 15/Feb/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: New Feature
Reporter: Andrew Schetinin Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Currently, when running "gradle build -i", it only says PASSED for every unit test.

It would be nice to see how much time each unit test took (like it is reported when running unit tests in Eclipse.

Actually my real goal is to detect most time-consuming unit tests and rewrite them... so may be there is another, better approach...

 Comments   
Comment by René Gröschke (Inactive) [ 15/Feb/11 ]

you can simply add this output to your test task:

test{
afterTest

{ descr, result -> def time = result.endTime - result.startTime logger.info("Test: $descr.className takes $time ms.") }

}

Comment by Andrew Schetinin [ 17/Feb/11 ]

Thanks a lot! It works like charm

I've only added $descr.name to the printed line in order to get a test function name along with a test class name (which was repeated several times):

logger.info("Test: $descr.className $descr.name takes $time ms.") }

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:54:17 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.