This message was deleted.
# plugin-development
s
This message was deleted.
t
Those tests are also meant to use ProjectBuilder, aren't they?
Also, constants (configuration names, or error messages)
v
As far as I understand, the unit tests are supposed to use
ProjectBuilder
, the functional tests are supposed to use TestKit.
👍 1
That's also what the two generated test cases do. The unit test case is using
ProjectBuilder
, the functional test case is using TestKit
And I wouldn't use configuration names or error messages from production for assertions in the functional tests, would you? This way you wouldn't catch unintended breaking changes.
j
I think what
init
is doing here is wrong 🙂
👌 1
t
Might actually just be an artifact of how the build scripts are generated: generator does an
addTestSuite("integrationTest")
that's implemented with an
implementation(project())
unconditionally (well, unless it's the default test suite). https://github.com/gradle/gradle/blob/master/platforms/software/build-init/src/mai[…]init/plugins/internal/JvmGradlePluginProjectInitDescriptor.java https://github.com/gradle/gradle/blob/4aa9831468479e6f076f668c3f10934dc1ca0571/pla[…]a/org/gradle/buildinit/plugins/internal/BuildScriptBuilder.java