[GRADLE-1096] improve integration testing of custom tasks/plugins Created: 05/Aug/10  Updated: 27/Jan/17  Resolved: 12/Feb/16

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 2.6-rc-1

Type: Improvement
Reporter: Russ Rollins Assignee: Unassigned
Resolution: Fixed Votes: 0


Task dependencies are not currently being exercised when testing via ProjectBuilder created Project instances. See http://j.mp/aaZBTk for more information.

Per Adam's response in that thread:

We're certainly missing some testing support at the higher levels. Perhaps something like:

  • A fixture at the same level as GradleLauncher, for writing integration tests at the command-line level. At this level, the test sets up a test build on the file system, runs the build, and then makes some assertions about what happened.
  • Something between that and ProjectBuilder, where the test sets up the model programmatically, runs a task (and implicitly its dependencies), and then makes some assertions about what happened.

Comment by Mark Vieira (Inactive) [ 12/Feb/16 ]

I believe the Gradle TestKit has sufficiently addressed this issue.

Generated at Wed Jun 30 11:46:47 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.