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
TestEngineis 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
TestEnginecan use to discover tests - Discovery Filters: filters that should be applied
by
TestEnginesduring 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
LauncherafterTestEngineshave performed test discovery. All of them have to include aTestDescriptorfor it to end up in the test plan.
This interface is not intended to be implemented by clients.
- Since:
- 1.0
- See Also:
-
Method Summary
Modifier and TypeMethodDescriptiondefault LauncherDiscoveryListenerGet theLauncherDiscoveryListenerfor this request.Get theEngineFiltersfor this request.Get thePostDiscoveryFiltersfor this request.Methods inherited from interface org.junit.platform.engine.EngineDiscoveryRequest
getConfigurationParameters, getFiltersByType, getOutputDirectoryProvider, getSelectorsByType
-
Method Details
-
getEngineFilters
List<EngineFilter> getEngineFilters()Get theEngineFiltersfor 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
EngineFiltersfor this request; nevernullbut potentially empty
-
getPostDiscoveryFilters
List<PostDiscoveryFilter> getPostDiscoveryFilters()Get thePostDiscoveryFiltersfor this request.The returned filters are to be combined using AND semantics, i.e. all of them have to include a
TestDescriptorfor it to end up in the test plan.- Returns:
- the list of
PostDiscoveryFiltersfor this request; nevernullbut potentially empty
-
getDiscoveryListener
Get theLauncherDiscoveryListenerfor 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:
getDiscoveryListenerin interfaceEngineDiscoveryRequest- Returns:
- the discovery listener; never
null - Since:
- 1.6
-