Interface TestDistributionConfiguration
Please refer to the user manual for details.
- Since:
- 3.17
-
Nested Class Summary
Nested ClassesModifier and TypeInterfaceDescriptionstatic interfaceA set of criteria for specifying which tests must run on local or remote executors only. -
Method Summary
Modifier and TypeMethodDescriptionWhether test distribution is enabled.Whether Test Distribution should fall back to regular execution, if JUnit Platform is not enabled.The set of criteria for specifying which tests must always run on local executors.The number of executors to use for running tests on this machine.The maximal number of remote executor failures that will be tolerated, before attempting to fall back to local executionThe number of remote executors that should be requested from the remote test execution infrastructure in order run the tests of this test task.If enabled, remote executors are tried first, falling back to local ones afterwaitTimeoutexpires.The set of criteria for specifying which tests must always run on remote executors.The requirements that need to be fulfilled by executors in order to execute the tests of this test task.If enabled, the tests will be retried in the same JVM.The duration the build waits for the remote test execution infrastructure to respond.voidlocalOnly(Action<? super TestDistributionConfiguration.RestrictedExecutionCriteria> action) The set of criteria for specifying which tests must always run on local executors.voidremoteOnly(Action<? super TestDistributionConfiguration.RestrictedExecutionCriteria> action) The set of criteria for specifying which tests must always run on remote executors.
-
Method Details
-
getEnabled
Whether test distribution is enabled.This setting defaults to
false.- Returns:
- whether test distribution is enabled
-
getMaxLocalExecutors
The number of executors to use for running tests on this machine.This setting defaults to
maxParallelForks. The number of local executors that can be used is limited bymaxWorkerCount. Setting this to 0 causes tests to be only executed on the remote test execution infrastructure.- Returns:
- the number of local executors to use.
-
getMaxRemoteExecutors
The number of remote executors that should be requested from the remote test execution infrastructure in order run the tests of this test task.This setting has no default value meaning that as much remote executors as are possible should be requested. Setting this to zero causes tests to be only executed using local executors.
Note that setting this to a fixed number doesn't necessarily mean that this test task will get that many remote executors. It's just an indicator for the remote test execution infrastructure for how many executors it should try to make available to this test task. It may well be that this test task does not get any remote executors at all e.g. if no executors matching all
requirementsbecome available.- Returns:
- the number of remote executors to request.
-
getRemoteExecutionPreferred
If enabled, remote executors are tried first, falling back to local ones afterwaitTimeoutexpires.This setting defaults to
false.- Returns:
- whether remote executors should be preferred over local executors
-
getWaitTimeout
The duration the build waits for the remote test execution infrastructure to respond.This setting defaults to 30 seconds and must be set to a positive value.
- Returns:
- the wait timeout duration.
-
getRetryInSameJvm
If enabled, the tests will be retried in the same JVM.This setting defaults to
true.- Returns:
- whether to retry tests in the same JVM
-
getRequirements
The requirements that need to be fulfilled by executors in order to execute the tests of this test task.Requirements are matched against the capabilities of the connected remote executors. Only those executors having all required capabilities will be assigned for running the tests of this task. Local executors are assumed to provide any capabilities. This means that no matter the requirements, local executors will always be used as long as
maxLocalExecutorsis greater than 0.A requirement String may only contain alphanumeric characters, dashes, underscores, periods, and a single equals sign. Apart from that, users are free in how they want to structure requirements. The recommendation is to use key value pairs or tag-like requirements:
test { distribution { requirements = ['os=linux', 'db=mysql', 'EXECUTOR_POOL_1'] } }The requirements will always have the value
jdk=<version>added with<version>being derived from the executable set on this test task viaTest.getExecutable().- Returns:
- the requirements remote executors need to fulfill for running tests of this test task.
-
getFallbackToRegularExecutionOnMissingPrerequisites
Whether Test Distribution should fall back to regular execution, if JUnit Platform is not enabled. -
getLocalOnly
The set of criteria for specifying which tests must always run on local executors. -
localOnly
The set of criteria for specifying which tests must always run on local executors. -
getRemoteOnly
The set of criteria for specifying which tests must always run on remote executors. -
remoteOnly
The set of criteria for specifying which tests must always run on remote executors. -
getMaxRecoverableFailures
The maximal number of remote executor failures that will be tolerated, before attempting to fall back to local execution
-