[GRADLE-2843] Enclosed JUnit tests are executed and reported twice Created: 20/Jul/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 3


I am using gradle-1.6 and added some junit tests.

One of my test classes is using the the Enclosed runner. Here is an [example]([1]https://github.com/junit-team/junit/w...). When I run the test (gradle test), it counts the test twice - once for the inner class and another for the enclosing class. Here is an example:

[1] https://github.com/junit-team/junit/wiki/'Enclosed'-test-runner-example
[2] https://d2r1vs3d9006ap.cloudfront.net/s3_images/927755/45.png?1374172555

Comment by Chad Blair [ 05/Nov/14 ]

The issue title should be "Enclosed JUnit tests are executed twice" (not just reported).

Gradle 2.2-rc-2

Build time: 2014-11-03 17:04:04 UTC
Build number: none
Revision: aab8521f1fd9a3484cac18123a72bcfdeb7006ec

Groovy: 2.3.6
Ant: Apache Ant(TM) version 1.9.3 compiled on December 23 2013
JVM: 1.8.0_25 (Oracle Corporation 25.25-b02)
OS: Linux 3.13.0-39-generic amd64

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