anchor.diff:  * Sources
   * Dependencies
   
  -In the future, the dimensions specified in the test suite may imply which toolchains are used to compile and run tests.
  +In the future, other properties may be specified in the test suite which may influence the toolchains selected to compile and run tests.
   
   The `Test` task associated with the target inherits its name from the suite.  Other properties of the `Test` task are configurable.
   
  
positive.code: A test suite is a collection of JVM-based tests.
  
  ==== Test Suite Target ====
  For the initial release of this plugin, each test suite has a single target.  This results in a 1:1:1 relationship between test suite, test suite target and a matching link:{groovyDslPath}/org.gradle.api.tasks.testing.Test.html[Test] task.  The name of the `Test` task is derived from the suite name.  Future iterations of the plugin will allow defining multiple targets based on a `dimension`, such as a particular JDK/JRE against which to execute tests.
  
  Each test suite has some configuration that is common across for all tests contained in the suite:
  
  
negative.code:  * A test suite named `test` (type: link:{groovyDslPath}/org.gradle.api.plugins.jvm.JvmTestSuite.html[JvmTestSuite]).
   * A `test` link:{groovyDslPath}/org.gradle.api.tasks.SourceSet.html[SourceSet].
   * Several configurations derived from the `test` SourceSet name: `testImplementation`, `testCompileOnly`, `testRuntimeOnly`
   * A single test suite target backed by a task named `test`.
  
  The `test` task, SourceSet and derived configurations are identical in name and function to those used in prior Gradle releases.
  
  