maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SUREFIRE-1306) JUnit4RerunFailingTestsIT does not execute with the JUnit version configured in the test
Date Wed, 30 Nov 2016 23:38:58 GMT

     [ https://issues.apache.org/jira/browse/SUREFIRE-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tibor Digana closed SUREFIRE-1306.
----------------------------------
    Resolution: Fixed

https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=15b953000afc26ca3844af7d18fd7b3c9ad26cd5

https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=195e4833ca7abb0278d34bff94cd7669d5331e45

> JUnit4RerunFailingTestsIT does not execute with the JUnit version configured in the test
> ----------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1306
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1306
>             Project: Maven Surefire
>          Issue Type: Test
>            Reporter: Benedikt Ritter
>            Assignee: Tibor Digana
>             Fix For: 2.19.2
>
>
> All the test methods in JUnit4RerunFailingTestsIT set JUnit Version explicitly to 4.7
by calling {{setJUnitVersion( "4.7" )}}. This will in turn set the system property {{junit.version}}.
The problem with this is, that the pom.xml in the test project (junit4-rerun-failing-tests)
uses the property {{junitVersion}} instead. The version is set to 4.4 in pom.xml. Furthermore
using JUnit 4.7 version in pom.xml results in test failures.
> Suggested solution: Drop the {{junitVersion}} property from pom.xml and use {{junit.version}}
instead, making it possible to set the version from the test cases. Use version 4.12, since
there seems to be a regression in 4.7 causing the test to fail with this version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message