maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clark Perkins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1553) @Unroll forces usage of JUnit Vintage
Date Tue, 06 Aug 2019 16:41:00 GMT

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

Clark Perkins commented on SUREFIRE-1553:
-----------------------------------------

I'm running into this issue, but also finding that I frequently see "[INFO] Running JUnit
Vintage" in the logs more than once - and the last one overwrites the "TEST-JUnit Vintage.xml"
file for all the previous ones, so I lose the record of some of my tests.

> @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.14#76016)

Mime
View raw message