How to use featureWithDefaultName method of io.cucumber.core.plugin.FeatureFileLoader class

Have you tried with version 1.1.42?

By principle, Cucumber doesn't supports data from external files. Instead it encourages to provide examples with scenario. However there are few non standard way available with cucumber to use examples from the external file. One of them, you can refer in grasshopper's post.

Another alternate is using gherkin with QAF which provides lots of features inbuilt data-providers including XML/CSV/JSON/EXCEL/DB. Here is the step-by-step-tutorial to start with.

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

1. While fresh run pass rerun plugin as an argument "-p", "rerun:target/cucumber/rerun.txt". This will generate cucumber rerun file which has line numbers of failed scenarios.
2. Then next time instead of features directory pass rerun text file "@target/cucumber-reports/rerun.txt"
3. This will re-run only your failed scenarios

If you are using cucumber options [I am not sure but I guess this was planned for deprecation] via junit runner then do as below.

Fresh run :

@CucumberOptions(features = {"src/test/resources/"},
    plugin = {"pretty", "json:target/cucumber/cucumber.json",
        "rerun:target/cucumber-reports/rerun.txt"})

Rerun :

        @CucumberOptions(
            features = {"@target/cucumber/rerun.txt"},
            plugin = {"pretty", rerun:target/cucumber/rerun.txt"})

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

Try using a more recent version of Serenity (the latest is 1.9.7).

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

The issue was traced to the browserTimeout parameter in the grid config.

You're using the wrong value for parallel. You have to set it to methods or both. Otherwise Surefire will run all tests of your runner class serially.

https://github.com/cucumber/cucumber-jvm/tree/main/cucumber-junit

Cucumber JUnit supports parallel execution of feature files across multiple threads. To enable this with maven set the parallel property to either methods or both.

<build>
    <plugins>
        <plugin>
            <artifactId>maven-surefire-plugin</artifactId>
            <!-- Use 2.22.1 or higher -->
            <version>${maven-surefire-plugin.version}</version>  
            <configuration>
                <parallel>both</parallel>
                <threadCount>4</threadCount>
            </configuration>
        </plugin>
    </plugins>
</build>