[
https://issues.apache.org/jira/browse/SUREFIRE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026770#comment-16026770
]
Tibor Digana edited comment on SUREFIRE-1372 at 5/26/17 8:13 PM:
-----------------------------------------------------------------
[~mpkorstanje]
Do we really need to wait for {{cucumber-jvm:2.0.0}}?
I knew I lost some ticket from my view. It was this.
I would like to assign this fix to version {{2.20.1}} but we would need to have
integration test(s); otherwise I may lose it again.
If you are sure {{cucumber-jvm:2.0.0}} is going to be released you can prepare
IT with {{2.0.0-SNAPSHOT}} version. We would need to have one commit in this
feature, so you can always amend latest commit which would be the way to follow
with surefire {{2.20.1}}.
was (Author: tibor17):
[~mpkorstanje]
Do we really need to wait for {{cucumber-jvm:2.0.0}}?
I knew I lost some ticket from my view. It was this.
I would like to assign this fix to version {{2.20.1}} but we would need to have
integration test(s); otherwise I may lose it again.
If you are sure {{cucumber-jvm:2.0.0}} is going to be released you can prepare
IT with {{2.2.0-SNAPSHOT}} version. We would need to have one commit in this
feature, so you can always amend latest commit which would be the way to follow
with surefire {{2.20.1}}.
> Rerunning failing tests fails in combination with
> Description#createSuiteDescription
> ------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 2.20
> Reporter: M.P. Korstanje
> Assignee: Tibor Digana
>
> When using surefire to rerun failing tests created by a Runner that uses
> {noformat}Description#createSuiteDescription{noformat} with a human readable
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create
> test class 'Scenario: Fail when running'
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
