This message was deleted.

I would just use

ProjectBuilder

here, but my plugin also adds dependencies from catalogs it assumes exists

For GradleRunner you are sadly left to check the output state of the build - files created, log entries, etc.

Yeah this is what I was afraid of - I think I'll have to create fakes for

VersionCatalogExtension

,

VersionCatalog

, etc

Not sure that fakes are needed. You need to provide GeadleRunner a (possibly generated) contrived build script to execute and check the results / log output.

Hmmm I could apply the plugin, register a task that prints what I want to verify, then assert on that, but that seems a bit... heavy

Yep. That’s the fugliness of GradleRunner. IMO there should be test support for grabbing parts of the model and doing standard assertions.