How to use toString method of net.serenitybdd.cucumber.suiteslicing.WeightedCucumberScenario class

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

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

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

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

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

First you have an exclusion for:

    <exclusions>
        <exclusion>
            <groupId>io.cucumber</groupId>
            <artifactId>cucumber-core</artifactId>
        </exclusion>
    </exclusions>

which should explain the "ClassNotFoundException: cucumber.runner.TimeServiceEventBus" error.

Further you have duplicate dependencies. You should really investigate all the warnings that Maven is giving you. And lastly, you are forcing possibly incompatible pieces of Serenity onto itself, by explicitly declaring individual bits of Serenity. Unless you have a particularly good reason for this, you should really avoid that!

In any case, the one simple dependency:

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

brings in everything you will need: all of Cucumber, all of Selenium, JUnit, and of course all of Serenity.

You can also use:

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

note the extra 4 there, if you want to use Cucumber version 4. Although last time I checked (admittedly it has been a while), this was still experimental.

See mvn dependency:tree to make sure.

PageObject has a getDriver() method, which you should use if you require the use of WebDriver.

I strongly suggest you study the Serenity BDD's Manual if you are going to work with the framework. You should find an answer to most questions there. Alternatively, check Serenity BDD Users Group.

First you have an exclusion for:

    <exclusions>
        <exclusion>
            <groupId>io.cucumber</groupId>
            <artifactId>cucumber-core</artifactId>
        </exclusion>
    </exclusions>

which should explain the "ClassNotFoundException: cucumber.runner.TimeServiceEventBus" error.

Further you have duplicate dependencies. You should really investigate all the warnings that Maven is giving you. And lastly, you are forcing possibly incompatible pieces of Serenity onto itself, by explicitly declaring individual bits of Serenity. Unless you have a particularly good reason for this, you should really avoid that!

In any case, the one simple dependency:

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

brings in everything you will need: all of Cucumber, all of Selenium, JUnit, and of course all of Serenity.

You can also use:

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

note the extra 4 there, if you want to use Cucumber version 4. Although last time I checked (admittedly it has been a while), this was still experimental.

See mvn dependency:tree to make sure.

You can use tagging for that purpose. Information about that feature can be found in Serenity BDD official documentation.

Just a short excerpt, tags are added to jUnit tests using WithTag annotation. The following will add a tag of type feature (this is a default Serenity type) with name Reporting:

@WithTag(type="feature", name="Reporting")

Then you can run tests with this tag with jUnit like this:

mvn clean verify -Dtags="feature:Reporting"

The dependency is into the plugin in POM.xml:

<plugin>
            <groupId>net.serenity-bdd.maven.plugins</groupId>
            <artifactId>serenity-maven-plugin</artifactId>
            <version>${serenity.version}</version>
            <dependencies>
                <dependency>
                    <groupId>net.serenity-bdd</groupId>
                    <artifactId>serenity-core</artifactId>
                    <version>${serenity.version}</version>
                </dependency>
            </dependencies>

The dependencies should be between the rest of dependencies . . . .

Try to remove that dependency and past it into the dependencies, not in the plugin section.

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.