How to use batches method of net.serenitybdd.cucumber.suiteslicing.SerenityTags class

Eventually I discovered that I had first to setup the Failsafe plugin, and then make it communicate with the CucumberMain class. Then, from the CLI, executing either mvn verify or mvn test with the list of tests that I want to execute made the trick

I modified my project and added the feature files, following the Cucumber/Serenity conventions. All the scenarios with Scenario Outline are showing up in the report. Please create the project like : https://github.com/cliviu/serenity-cucumber5-starter.git. Please refer to the git issue:- https://github.com/serenity-bdd/serenity-core/issues/2190

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

The above problem was solved by using following combination of dependencies:

    <dependencies>

    <dependency>
        <groupId>net.serenity-bdd</groupId>
        <artifactId>serenity-cucumber</artifactId>
        <version>${serenity.version}</version>
    </dependency>

    <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>4.13.2</version>
    </dependency>

    <dependency>
        <groupId>org.jeasy</groupId>
        <artifactId>easy-random-core</artifactId>
        <version>5.0.0</version>
    </dependency>

    <dependency>
        <groupId>org.apache.poi</groupId>
        <artifactId>poi-ooxml</artifactId>
        <version>5.2.2</version>
    </dependency>

    <dependency>
        <groupId>org.apache.logging.log4j</groupId>
        <artifactId>log4j-core</artifactId>
        <version>2.17.2</version>
    </dependency>

    <dependency>
        <groupId>com.googlecode.json-simple</groupId>
        <artifactId>json-simple</artifactId>
        <version>1.1.1</version>
    </dependency>

    <dependency>
        <groupId>com.github.javafaker</groupId>
        <artifactId>javafaker</artifactId>
        <version>1.0.2</version>
    </dependency>

</dependencies>

A ConsoleAppender won't write to a file, and will just ignore the file configuration element under it. Instead, you should use a FileAppender:

<configuration>
    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
        <encoder>
            <pattern>
                %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg..................%n
            </pattern>
        </encoder>
    </appender>
    <appender name="FILE" class="ch.qos.logback.core.FileAppender">
        <file>admin.log</file>
        <encoder>
            <pattern>
                %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg..................%n
            </pattern>
        </encoder>
    </appender>
    <logger name="root" level="DEBUG" />
    <logger name="net.serenitybdd" level="INFO" />
    <logger name="net.thucydides" level="INFO" />
    <root level="INFO">
        <appender-ref ref="STDOUT" />
        <appender-ref ref="FILE" />
    </root>
</configuration>

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

compile group: 'org.seleniumhq.selenium', name: 'selenium-chrome-driver', version: '3.0.1'

I'm not using Selenium. I'm using Gradle, Cucumber, Serenity.

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.

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