Problem with testSets in multi project build about gradle-testsets-plugin HOT 2 CLOSED

Hi,

thanks for the report! I've never tried to configure subprojects like this, but I think it's a general issue with how Gradle / Groovy works.

What happens here is this:

• the plugin gets applied on the root project, creating a task called integrationTest
• in the subproject testSets block, you would usually just spell the name of the item to create, triggering methodMissing which in turn leads to Gradle creating the item. This is some of the Groovy magic that Gradle does.
• However, since integrationTest is already a known symbol in an enclosing scope (tasks are available as properties on the project), it will never trigger methodMissing on the testset container, but just use the task as an expression. Which, of course, does nothing.

If you replace integrationTest with create('integrationTest') in the subproject, then it will work. I'm afraid there isn't much I can do about it, it's just how Gradle works.

from gradle-testsets-plugin.

If I understand you correctly, one should define it the following way if indeed the subproject should have test-set with same name as test-set in root project:

plugins {
	id 'java'
	id 'org.unbroken-dome.test-sets' version '2.0.1'
}

testSets { integrationTest }

project (":subproject") {
	apply plugin: 'java'
	apply plugin: 'org.unbroken-dome.test-sets'
	testSets { create('integrationTest') }
}

Is that right?

Would you please be so kind as to document this in the Usage section of the documentation?

Thank you.

Tomas Rohrbacher

from gradle-testsets-plugin.