JenkinsTestSuiteExtension

Extension added to every JvmTestSuite by the shared-library plugin.

When useTestHarness is true the suite receives full Jenkins test-harness wiring: jenkins-test-harness on the implementation classpath, HPI archives and the WAR on the test runtime classpath, per-suite WarExploder output directory, system-property injectors for the library name/location/WAR path, and JVM flags required by Jenkins' reflection-heavy internals.

Set useTestHarness directly inside a register<JvmTestSuite> block:

testing {
suites {
register<JvmTestSuite>("integrationTestKotest") {
jenkins.useTestHarness = true
}
}
}

The built-in integrationTest suite is enabled automatically. The test suite is always disabled (it uses jenkins-pipeline-unit, not the full harness).

Constructors

Link copied to clipboard
constructor()

Properties

Link copied to clipboard
abstract val useTestHarness: Property<Boolean>