maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clark Perkins (JIRA)" <>
Subject [jira] [Commented] (SUREFIRE-1553) @Unroll forces usage of JUnit Vintage
Date Mon, 12 Aug 2019 02:43:00 GMT


Clark Perkins commented on SUREFIRE-1553:

Also I just looked at the TEST-com.skrser.surefire.CalculatorTest.xml file - and it's missing
the test names:

<testcase name="" classname="com.skrser.surefire.test.CalculatorSpockTest" time="0.078"/>
<testcase name="" classname="com.skrser.surefire.test.CalculatorSpockTest" time="0"/>
<testcase name="" classname="com.skrser.surefire.test.CalculatorSpockTest" time="0.084"/>
<testcase name="multiply" classname="com.skrser.surefire.CalculatorTest" time="0.001"/>{noformat}

> @Unroll forces usage of JUnit Vintage
> -------------------------------------
>                 Key: SUREFIRE-1553
>                 URL:
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: JUnit 5.x support, Maven Surefire Plugin
>    Affects Versions: 2.22.0
>            Reporter: Sergey Skryabin
>            Assignee: Tibor Digana
>            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

View raw message