maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <>
Subject [jira] [Commented] (SUREFIRE-1553) @Unroll forces usage of JUnit Vintage
Date Tue, 13 Aug 2019 22:34:00 GMT


Tibor Digana commented on SUREFIRE-1553:

I have observed the same results. Maybe you should help us and debug the class {{org.apache.maven.surefire.junitplatform.RunListenerAdapter}}
and we will concentrate on another issues where you cannot. This will speed up the release.
I do not know where the problem is but the debugger will uncover more.

> @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