[GRADLE-2353] testng options includeGroups and suites do not play together well Created: 14/Jun/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Provided a testng suite xml:
<code>
<suite name="INTEGRATION_SUITE">
<test name="suiteA" preserve-order="true">
<classes>
<class name="gradletest0.Gradle0Test"/>
<class name="gradletest0.Gradle1Test"/>
</classes>
</test>
<test name="suiteB" preserve-order="true">
<classes>
<class name="gradletest0.Gradle15Test"/>
<class name="gradletest0.Gradle16Test"/>
</classes>
</test>
</suite>
</code>

If above suite is used along with includeGroups property, e.g.

test {
  useTestNG()
  options.suites 'theSuite.xml'
  options.includeGroups 'someGroup'
}

Then the 'someGroup' criteria is only applied to 'suiteA' (see the xml above). I would expect it to be applied to all suites (suiteA and suiteB) or not applied at all / fail + document that the 2 options don't work together.

I briefly looked at the code and I don't see anything specific on the Gradle side. We only feed the 3rd party TestNG instance with the suite files and with group names that should be included. So the bug might be outside Gradle.

 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 12:19:35 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.