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] [Comment Edited] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription
Date Sat, 27 May 2017 04:46:04 GMT

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

Tibor Digana edited comment on SUREFIRE-1372 at 5/27/17 4:45 AM:
-----------------------------------------------------------------

[~mpkorstanje]
Ok, lets try to use latest cucumber release version without having {{2.0.0-SNAPSHOT}} and
run the build of surefire {{mvn install -P run-its}}. Is the build successful?
Is there any way of using {{CucumberOptions}} with re-run in the old release versions of cucumber?
Any drawback?
Maybe the users of surefire and Cucubmer would prefer some documentation in surefire if current
{{CucumberOptions}} are possible.


was (Author: tibor17):
[~mpkorstanje]
Ok, lets try to use latest cucumber release version without having {{2.0.0-SNAPSHOT}} and
run the build of surefire {{mvn install -P run-its}}. Is the build successful?
Is there any way using {{CucumberOptions}} in re-run?
Any drawback?
Maybe the users of surefire and Cucubmer would prefer some documentation in surefire if current
{{CucumberOptions}} are possible.

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

Mime
View raw message