[Commented] (SUREFIRE-1553) @Unroll forces usage of JUnit Vintage

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Commented] (SUREFIRE-1553) @Unroll forces usage of JUnit Vintage

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SUREFIRE-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615447#comment-16615447 ]

Tibor Digana commented on SUREFIRE-1553:

[~[hidden email]]
The Vintage must be activated always according to user's POM. Am I right?
Why there is report file {{TEST-JUnit Vintage.xml}} and not {{TEST-CalculatorTest.xml}}?

> @Unroll forces usage of JUnit Vintage
> -------------------------------------
>                 Key: SUREFIRE-1553
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1553
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: JUnit 5.x support, Maven Surefire Plugin
>    Affects Versions: 2.22.0
>            Reporter: Sergey Skryabin
>            Priority: Major
> If run
> {code}mvn clean test{code}
> JUnit4 tests and Spock tests (which not contain @Unroll) are executed normally. Once Spock test with @Unroll annotation appears, then Surefire execute
> {code}[INFO] Running JUnit Vintage{code}
>  and all other JUnit4 tests and Spock tests are wrapped with this runner.
> In surefire-reports I see _TEST-<all tests executed before meeting @Unroll>.xml_ s and than
> _TEST-JUnit Vintage.xml_
> Though it could be done by intention, behaviour is different from 2.21.0 (no wrapping with Vintage). Also it much more visible to have separate reports per test class (both in console output and surefire-reports folder).

This message was sent by Atlassian JIRA