Test fixtures dependencies not possible in dependency block of test suite plugin

[toerni]

While testing the new test-suite plugin, I tried to add a dependency to the test-fixtures of another project in the new dependency block using kotlin dsl

Expected Behavior

Expecting the dependency below to compile

testing {
    suites {

        val integrationtest by registering(JvmTestSuite::class) {
            this.useJUnitJupiter()


            dependencies {
                implementation(platform(testfixtures(":myProject")))
            }
            
            targets {
                all {
                    testTask.configure {
                        shouldRunAfter(tasks.named("test"))
                        testLogging {
                            events(FAILED, SKIPPED)
                            exceptionFormat = TestExceptionFormat.FULL
                        }
                    }
                }
            }
        }
    }
}

Current Behavior

testfixtures dependency does not compile in script plugin in buildSrc

Your Environment

• gradle 7.3
• jvm-test-suite plugin

[brizzbuzz]

any update on this? kind of a blocker for larger projects wanting to use the test suite API :(

[brizzbuzz]

Also kinda curious... beyond the need for being able to import external fixtures, it seems weird that even for the fixtures in the same module, this still doesn't work.

From the fixtures docs here

This will automatically create a testFixtures source set, in which you can write your test fixtures. Test fixtures are configured so that:
they can see the main source set classes
test sources can see the test fixtures classes

Shouldn't new test suites fall under the category of test sources?

[brizzbuzz]

A quick test seems to indicate that this is a viable work around, but it feels... wrong

testing {
  suites {
    val testIntegration by creating(JvmTestSuite::class) {
      useJUnitJupiter()
      dependencies {
        // Project
        implementation(project)
        implementation(project.dependencies.testFixtures(project))
        // ...

[Vampire]

Actually it is probably the same issue as #19065 and the same work-arounds should apply, just that the other ticket is about platform and this about testFixtures. But in both cases the problem is, that the type is different in this dependencies block and that the extensions functions are only defined for the other type.

[SgtSilvio]

The same applies for annotationProcessor

[tresat]

I'm closing this issue, as it is covered by: #19472

[SgtSilvio]

@tresat what about annotationProcessor dependencies, should I create a new issue for that?

[tresat]

No need, see: #20115