maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (Jira)" <>
Subject [jira] [Commented] (SUREFIRE-1724) Support JUnit Platform DiscoverySelectors
Date Fri, 22 Nov 2019 18:33:00 GMT


Tibor Digana commented on SUREFIRE-1724:

I want to use the discovery via {{LauncherDiscoveryRequestBuilder}} excluding the system classloader.
I guess this implementation of {{LauncherDiscoveryRequestBuilder}} takes a look in the classpath
or the classloader. I don't want this because i don't want the classes been loaded while performing
the discovery phase. Do you think that {{LauncherDiscoveryRequestBuilder}} can operate over
a list of JAR file, means their Path-s of location?

> Support JUnit Platform DiscoverySelectors 
> ------------------------------------------
>                 Key: SUREFIRE-1724
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Improvement
>            Reporter: M.P. Korstanje
>            Priority: Major
> The JUnit Platform defines multiple [DiscoverySelectors|]
to discover tests in different locations. This allows TestEngines to discover tests in classes,
the class path root, resource root, files, ect.
> Currently Surefire supports TestEngine implementations  through the JUnitPlatformProvider.
However the JUnitPlatformProvider only issues discovery requests for classes that have already
been discovered by Surefire. Additionally if no tests were discovered by Surefire then no
test discovery requests will be issued at all.
> This means that Surefire does not fully utilize the discovery capabilities of the JUnit
Platform and makes it impossible to use the JUnitPlatformProvider for test frameworks that
do not have class based tests such as Cucumber.
> To make Cucumber work at the very least the class path root discovery selector would
have to be supported.

This message was sent by Atlassian Jira

View raw message