} else {
                printer.printStatement(builder.suiteRegistration("Create a new test suite", builder.block.testing, name, JvmTestSuite.class.getSimpleName(), buildSuiteConfigurationContents()));
            }
        }

See link:{groovyDslPath}/org.gradle.api.plugins.jvm.JvmComponentDependencies.html[JvmComponentDependencies] and link:{groovyDslPath}/org.gradle.api.plugins.jvm.JvmTestSuite.html[JvmTestSuite] for an example of how this is used in a Gradle core plugin.

==== 1. Create an interface that extends `Dependencies`

            </tr>
            <tr>
                <td>org.gradle.testing.base.TestSuite</td>
            </tr>
            <tr>
                <td>org.gradle.api.plugins.jvm.JvmTestSuite</td>
            </tr>
            <tr>
                <td>org.gradle.testing.base.TestSuiteTarget</td>
            </tr>
            <tr>
                <td>org.gradle.api.plugins.jvm.JvmTestSuiteTarget</td>

In some cases, this requires syntax changes.
For example, build scripts that previously added Test Suite dependencies with the following syntax:

```kotlin
testing {
  suites {
    register<JvmTestSuite>("integrationTest") {
      dependencies {
        implementation(project)
      }
    }
  }
}
```

will now fail to compile, with a message like:

```

=====
[.multi-language-sample]
======
.build.gradle.kts
[source,kotlin]
----
plugins {
    id("java-library")
}

testing.suites {
    named<JvmTestSuite>("test") {
        dependencies {
            // Dependency is declared on a `DependencyCollector`
            implementation("com:foo")
        }
    }
}

configurations.testImplementation {