That will be helpful for debug purpose. I need similar functionality as well to debug some fragile test which only failed when you run all tests in a batch.

This is a serious limitation of gradle, and a reason that I would not likely choose it in future projects. Please assign to someone asap. Thx.

This will be a really helpful feature for longer integration test runs.

yes this would be really helpful, because our integration test suit run takes up to one hour and it would really nice to get the information earlyer that there are any failing tests

+1 – very helpful to have this. This thread: http://bit.ly/2bufkos describes an attempt using TestListener.afterTest to no avail. Any suggestions on API to actually stop the runner and fail the build? Thanks.

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!

I'm still interested in an option to fail the build early if any test fails as that would allow developers to get quicker feedback from CI systems.

The feature is now tracked on GitHub: https://github.com/gradle/gradle/issues/1310