You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2023/01/07 08:45:00 UTC

[jira] [Updated] (SUREFIRE-1724) Support JUnit Platform DiscoverySelectors

     [ https://issues.apache.org/jira/browse/SUREFIRE-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated SUREFIRE-1724:
-------------------------------------
    Fix Version/s: 3.0.0-M9
                       (was: 3.0.0-M8)

> Support JUnit Platform DiscoverySelectors 
> ------------------------------------------
>
>                 Key: SUREFIRE-1724
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1724
>             Project: Maven Surefire
>          Issue Type: Improvement
>            Reporter: M.P. Korstanje
>            Priority: Major
>             Fix For: 3.0.0-M9
>
>
> The JUnit Platform defines multiple [DiscoverySelectors|https://junit.org/junit5/docs/5.0.2/api/org/junit/platform/engine/DiscoverySelector.html] 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
(v8.20.10#820010)