How to use featurePathWithPrefixIfNecessary method of io.cucumber.core.plugin.FeaturePathFormatter class

Below are the steps from John Ferguson Smart' blog, author of Serenity-BDD (considering that you have installed Cucumber for Java plugin).

Running Cucumber with Serenity feature files directly from IntelliJ:

IntelliJ provides excellent integrated support for Cucumber feature files. You can even run features simply by right-clicking on the feature file. But this won’t work when you are using Cucumber with Serenity, as Serenity needs to instrument the feature file before execution. Fortunately, this is easy to fix. Here’s how:

• Click on the feature file you want to run
• In the Run menu Select Run…
• In the contextual menu, select the feature, then “Edit…”
• You should now see the ‘Edit Configuration Settings’ window. Set the main class to ‘net.serenitybdd.cucumber.cli.Main’
• Change the Glue field to the root package of your project (or of your step definitions)
• Click Apply

Now you can run your feature directly by right-clicking on the feature file.

P.S. Not all versions of Cucumber for Java plugin works correctly, especially when you have just updated IntelliJ IDEA to the latest version. I can confirm that next setup works correctly:

• IntelliJ IDEA 2018.2.3 (Community version);
• Cucumber for Java plugion version 182.3934;
• net.serenity-bdd:serenity-core:2.0.6;
• net.serenity-bdd:serenity-cucumber:1.9.18

Reading other pages, I found the solution:

In my POM, modify the Serenity dependencies below

<!--SERENITY DEPENDENCIES-->
        <dependency>
            <groupId>net.serenity-bdd</groupId>
            <artifactId>serenity-core</artifactId>
            <version>1.2.5-rc.6</version>
        </dependency>
        <dependency>
        <groupId>net.serenity-bdd</groupId>
        <artifactId>serenity-junit</artifactId>
        <version>1.2.5-rc.6</version>
        </dependency>
        <dependency>
            <groupId>net.serenity-bdd</groupId>
            <artifactId>serenity-cucumber</artifactId>
            <version>1.1.29</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-simple</artifactId>
            <version>1.7.25</version>
        </dependency>
        <!--SERENITY DEPENDENCIES-->

Add the next configuration to the POM

<properties>
    <cucumber.version>1.2.5</cucumber.version>
    <serenity.version>1.2.5-rc.6</serenity.version>
    <serenity.cucumber.version>1.1.29</serenity.cucumber.version>
       <java.version>8</java.version>
   </properties>

And use this plugin:

<plugin>
                 <groupId>net.serenity-bdd.maven.plugins</groupId>
                 <artifactId>serenity-maven-plugin</artifactId>
                 <version>1.1.29</version>
                 <executions>
                     <execution>
                         <id>serenity-reports</id>
                         <phase>post-integration-test</phase>
                         <goals>
                             <goal>aggregate</goal>
                         </goals>
                     </execution>
                 </executions>
             </plugin>

After running my SerenityRunner, the system runs the feature classes without problem. This is the result of that:

[main] INFO net.serenitybdd.core.Serenity - 

        __    _____ _____ ____ _____   ____   _    ____  ____  _____ ____  
  _     \ \  |_   _| ____/ ___|_   _| |  _ \ / \  / ___|/ ___|| ____|  _ \ 
 (_)_____| |   | | |  _| \___ \ | |   | |_) / _ \ \___ \\___ \|  _| | | | |
  _|_____| |   | | | |___ ___) || |   |  __/ ___ \ ___) |___) | |___| |_| |
 (_)     | |   |_| |_____|____/ |_|   |_| /_/   \_\____/|____/|_____|____/ 
        /_/          

Thanks for the help Grasshopper!!!

Below are the steps from John Ferguson Smart' blog, author of Serenity-BDD (considering that you have installed Cucumber for Java plugin).

Running Cucumber with Serenity feature files directly from IntelliJ:

IntelliJ provides excellent integrated support for Cucumber feature files. You can even run features simply by right-clicking on the feature file. But this won’t work when you are using Cucumber with Serenity, as Serenity needs to instrument the feature file before execution. Fortunately, this is easy to fix. Here’s how:

• Click on the feature file you want to run
• In the Run menu Select Run…
• In the contextual menu, select the feature, then “Edit…”
• You should now see the ‘Edit Configuration Settings’ window. Set the main class to ‘net.serenitybdd.cucumber.cli.Main’
• Change the Glue field to the root package of your project (or of your step definitions)
• Click Apply

Now you can run your feature directly by right-clicking on the feature file.

P.S. Not all versions of Cucumber for Java plugin works correctly, especially when you have just updated IntelliJ IDEA to the latest version. I can confirm that next setup works correctly:

• IntelliJ IDEA 2018.2.3 (Community version);
• Cucumber for Java plugion version 182.3934;
• net.serenity-bdd:serenity-core:2.0.6;
• net.serenity-bdd:serenity-cucumber:1.9.18

Looks like you are indirectly running Serenity through the junit-vintage-engine. When executed this way, parallel execution is simply not supported.

To be exact you are running your tests through Surefire -> JUnit 5 -> JUnit Vintage -> JUnit 4 -> Serenity -> Cucumber.

You'd have to wait for JUnit Vintage to support parallel execution or get rid of JUnit 5 from your depencies so Surefire can run JUnit 4 directly.

However given that you are also using Spring you may not be able to get rid of JUnit 5.

You could ask Serenity to support JUnit 5 but I suspect they will be unable too. They have never bothered to contribute the extension points they'd need upstream. Instead they have hacked their stuff into Cucumber.

Honestly this type of error is tricky and it could be happening for multiple reasons (for example, having the runner, steps or features outside the test folder), however, based in the info you shared, try adding the name of the feature file in the path:

@RunWith(CucumberWithSerenity.class)
@CucumberOptions(features = "src/test/resources/features/yourfile.feature",
        glue = "stepdefinitions")

In case you have a directory inside the step definition folder, you must do:

@RunWith(CucumberWithSerenity.class)
@CucumberOptions(features = "src/test/resources/features/yourfile.feature",
            glue = "stepdefinitions/your_directory")

I would normally not answer my own question , but I see few similar questions on SO.

For my case, removing fixed the issue.
testCompile ("io.cucumber:cucumber-spring:6.10.4")

However, to get the correct version of dependencies, if you are stuck in such issue, is to refer there github and check release notes and dependency tee.

For my case, the issue was on Cucumber-Serenity5.

So getting the dependecncies from build.gradle, worked. https://github.com/serenity-bdd/serenity-cucumber5/blob/master/build.gradle

Please note, the actual versions are defined in, gradle.proporties.
https://github.com/serenity-bdd/serenity-cucumber5/blob/master/gradle.properties

Upgrade to Spring 4.2.1 and you should be able to use the Serenity runner:

http://docs.spring.io/spring/docs/4.2.1.RELEASE/spring-framework-reference/htmlsingle/#testcontext-junit4-rules

See https://github.com/serenity-bdd/serenity-core/#cucumber-4. I expect Serenity will only work with JUnit 5 in vintage mode.

This link should help, do not forget to give your definitions in glue section of the configuration.

https://johnfergusonsmart.com/running-cucumber-serenity-feature-files-directly-intellij/