runtimeOnly "org.elasticsearch.gradle:reaper:$version"
  testImplementation "com.puppycrawl.tools:checkstyle:${props.getProperty('checkstyle')}"
  testImplementation "junit:junit:${props.getProperty('junit')}"
  testImplementation 'com.github.tomakehurst:wiremock-jre8-standalone:2.23.2'
  testImplementation 'org.mockito:mockito-core:1.9.5'
  testImplementation "org.hamcrest:hamcrest:${props.getProperty('hamcrest')}"

        testImplementation.setPath(null);
        assertNull(testImplementation.getPath());

        // Test null UNC path components
        testImplementation.setFullUNCPath(null, null, null);
        assertNull(testImplementation.getDomain());
        assertNull(testImplementation.getServer());
        assertNull(testImplementation.getFullUNCPath());
    }

    @Test
    @DisplayName("Test with empty strings")

                apply(plugin = "java-library")
                repositories {
                    mavenCentral()
                }

                dependencies {
                    "testImplementation"("org.junit.jupiter:junit-jupiter-engine:5.8.1")
                    "testRuntimeOnly"("org.junit.platform:junit-platform-launcher")
                }

                tasks.named<Test>("test").configure {

should not be shipped with the project because it is "provided" by the runtime
somehow. Elasticsearch plugins use this configuration to include dependencies
that are bundled with Elasticsearch's server.</dd>
<dt>`testImplementation`</dt><dd>Code that is on the classpath for compiling tests
that are part of this project but not production code. The canonical example
of this is `junit`.</dd>
</dl>