maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription
Date Sun, 24 Dec 2017 09:05:00 GMT

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

ASF GitHub Bot commented on SUREFIRE-1372:
------------------------------------------

Github user Tibor17 commented on the issue:

    https://github.com/apache/maven-surefire/pull/150
  
    @mpkorstanje 
    The build passed successfully. I will refactor little details, I will squash our commits
and then I will push it to master.
    
    I could not find a documentation for configuring annotation `CucumberOptions`. For instance
we were using it like this `@CucumberOptions(features = {"classpath:flake"})` in your previous
commit. Why we do not use it any more and why it was important? Do you think it is important
for the users and important for proper functionality of Surefire?
    
    One more question I have is regarding artifacts of Cucumber. Which one is right to use:
    `<artifactId>cucumber-junit</artifactId>`
    `<artifactId>cucumber-java8</artifactId>`



> 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
>             Fix For: 2.21.1
>
>
> 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.4.14#64029)

Mime
View raw message