[GRADLE-1424] Better documentation of Test.useTestNG(Closure testFrameworkConfigure) Created: 05/Mar/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-1
Fix Version/s: None

Type: Improvement
Reporter: Kevin Stembridge Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

The current documentation for the Java plugin lists the Test.useTestNG(Closure testFrameworkConfigure) method but does not provide any information on how to specify options. Looking at the javadoc for this method (http://gradle.org/1.0-milestone-1/docs/javadoc/org/gradle/api/tasks/testing/Test.html#useTestNG(groovy.lang.Closure)) it says that the closure is passed a JunitOptions object. At runtime, it is actually getting passed a TestNGOptions object. There is no javadoc for TestNGOptions. The javadoc for the JunitOptions class doesn't list the available properties.

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