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

["Sergey Skryabin (JIRA)" <ji...@apache.org>]

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

Sergey Skryabin commented on SUREFIRE-1553:
-------------------------------------------

Hello [~tibor17] and [~sormuras@gmx.de]!

Here you can check the example to reproduce the issue: https://github.com/skrser/maven-surefire-unroll

> @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
(v7.6.3#76005)