[GRADLE-1341] Gradle's Test Scanner Ignores the presence of a TestNG suite.xml file. Created: 24/Jan/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Mike Cornell Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Attachments: File matyb-java-koans-7b6bb2c.tar.gz    


I first asked the question on Stack Overflow with the assumption that I was doing something wrong:


IMHO, when a suite.xml file is specified, Gradle should use it for execution. I'm guessing it doesn't in order to hook into the processing and tell when a failure has occured.

test {

  1. Adding
  2. scanForTestClasses = false
  3. causes zero tests to be executed, since the class names don't end in Test

My suite.xml file specified the exact sequence of each test class to run. Each test class contains an annotation on each method to specify the order in which the tests will be run. When I place specific logging in IMethodListener, it is evident that it does not execute.

In addition, my other Listener is also getting clobbered. It produces specific logging to the screen and specifically the onStart() method is being ignored.

FWIW, Maven executes the use case properly without concern. Gradle is a better fit for this project due to the wrapper's ability to provide a user with a no effort configuration.

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