Module org.junit.platform.launcher
Package org.junit.platform.launcher
Interface LauncherDiscoveryRequest
- All Superinterfaces:
EngineDiscoveryRequest
@API(status=STABLE,
since="1.0")
public interface LauncherDiscoveryRequest
extends EngineDiscoveryRequest
LauncherDiscoveryRequest
extends the EngineDiscoveryRequest
API
with additional filters that are applied by the Launcher
itself.
Specifically, a LauncherDiscoveryRequest
contains the following.
- Engine Filters: filters that are applied before
each
TestEngine
is executed. All of them have to include an engine for it to contribute to the test plan. - Configuration Parameters: configuration parameters that can be used to influence the discovery process
- Discovery Selectors: components that select
resources that a
TestEngine
can use to discover tests - Discovery Filters: filters that should be applied
by
TestEngines
during test discovery. All of them have to include a resource for it to end up in the test plan. - Post-Discovery Filters: filters that will be
applied by the
Launcher
afterTestEngines
have performed test discovery. All of them have to include aTestDescriptor
for it to end up in the test plan.
- Since:
- 1.0
- See Also:
-
Method Summary
Modifier and TypeMethodDescriptiondefault LauncherDiscoveryListener
Get theLauncherDiscoveryListener
for this request.Get theEngineFilters
for this request.Get thePostDiscoveryFilters
for this request.Methods inherited from interface org.junit.platform.engine.EngineDiscoveryRequest
getConfigurationParameters, getFiltersByType, getSelectorsByType
-
Method Details
-
getEngineFilters
List<EngineFilter> getEngineFilters()Get theEngineFilters
for this request.The returned filters are to be combined using AND semantics, i.e. all of them have to include an engine for it to contribute to the test plan.
- Returns:
- the list of
EngineFilters
for this request; nevernull
but potentially empty
-
getPostDiscoveryFilters
List<PostDiscoveryFilter> getPostDiscoveryFilters()Get thePostDiscoveryFilters
for this request.The returned filters are to be combined using AND semantics, i.e. all of them have to include a
TestDescriptor
for it to end up in the test plan.- Returns:
- the list of
PostDiscoveryFilters
for this request; nevernull
but potentially empty
-
getDiscoveryListener
Get theLauncherDiscoveryListener
for this request.The default implementation returns a no-op listener that ignores all calls so that engines that call this methods can be used with an earlier version of the JUnit Platform that did not yet include it.
- Specified by:
getDiscoveryListener
in interfaceEngineDiscoveryRequest
- Returns:
- the discovery listener; never
null
- Since:
- 1.6
-