maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mpkorstanje <...@git.apache.org>
Subject [GitHub] maven-surefire issue #150: SUREFIRE-1372 Filter tests to be rerun by descrip...
Date Sun, 24 Dec 2017 17:30:12 GMT
Github user mpkorstanje commented on the issue:

    https://github.com/apache/maven-surefire/pull/150
  
    >  The build passed successfully. I will refactor little details, I will squash our
commits and then I will push it to master.
    
    Cheers.
    
    > I could not find a documentation for configuring annotation
    
    I've changed the layout of the project to match the default used by cucumber. When using
the default layout  `@CucumberOptions` is not needed. Cucumber uses the location of the runner
class to figure out where the features and glue are. 
    
    All in all  `@CucumberOptions` influences which features are included but doesn't change
how cucumber presents itself to surefire. From surefires perspective it should be yet another
junit test suite. 
    
    > One more question I have is regarding artifacts of Cucumber. Which one is right to
use:
    
    `cucumber-junit` provides integration with junit and should be used when junit is to be
used. `cucumber-java` provides java annotations to denote step definitions. `cucumber-java8`
depends on `cucumber-java` and adds lambda based step  definitions. Using `cucumber-java`
is sufficient.


---

Mime
View raw message