[GRADLE-999] Provide for different types of tests Created: 22/Jun/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Steve Ebersole Assignee: Unassigned
Resolution: Won't Fix Votes: 2


Even Gradle's own build could leverage this. Basically the functional requirements between different types of testing (unit, functional, integration, system, acceptance, etc) are different. Would be great to have built in support for wiring up the needed configurations and sourceSets for these other types of testing as well, not just unit testing ("test").

Especially as GRADLE-994 gets implemented, this becomes very very usable and powerful.

Comment by Hans Dockter [ 25/Jun/10 ]

One option would be to provide different type of source sets. Java, UnitTest, ... If you declare a unit test source set, the test task would be automatically created and be wired with the confs. The same possibly for other types of test.

Comment by Steve Ebersole [ 28/Jun/10 ]

In this vein, I tried what we discussed in terms of "matrix" style tests in terms of doing "apply" on a matrix.gradle file. This "works" up until the point that the dependencies are used. I build a classpath for the test task using

{configuration}.plus( some other stuff ). {configuration}

is the Configuration which contains the jdbc driver dependencies (I debugged and verified the proper dependency instances are there). However, running leads to an error that the JDBC driver class could not be found. Is this perhaps an issue that the dependency is not "resolved"?

Comment by Steve Ebersole [ 28/Jun/10 ]

Sorry, I was using the wrong method to add the dependency. I had been using project.getDependencies().module(...); switching to project.getDependencies().add(...) fixed this.

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