How to use isASingleBrowserScenario method of io.cucumber.core.plugin.FeatureTracker class

Have you tried with version 1.1.42?

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.

The problem seems to be in the @manual tag, probably a bug in the framework. It is fixed by adding 'and not @manual' when executing tests.

To anyone with this problem, already bypassed the problem with:

        theActorInTheSpotlight().attemptsTo(
                Ensure.that(FOO.value().answeredBy(theActorInTheSpotlight())).isEqualTo(bar)
        );

class FOO extends WebDriverQuestion implements Question<String> {
    @Override
    public String answeredBy(Actor actor) {
            return Text.of(XPATH_TARGET1).viewedBy(actor).asString();
    }
    public static FOO value(){
        return new FOO();
    }
}

I still want to know why initial code failed randomly.

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/

I was also facing issues in initiating safari browser on mac machine, and below solution helped me

if (browserType.equals("safari")) {
            // System.setProperty("webdriver.safari.driver", workingDir +
            // "//driver//SafariDriverServer.exe");
            System.setProperty("webdriver.safari.driver",
                    "/driver/SafariDriver.safariextz");
            System.setProperty("webdriver.safari.noinstall", "true");
            DesiredCapabilities desiredCapabilities = DesiredCapabilities
                    .safari();
            SafariOptions safariOptions = new SafariOptions();
            safariOptions.setUseCleanSession(true);
            safariOptions.getUseCleanSession();
            safariOptions.setUseCleanSession(true);
            desiredCapabilities.setCapability(SafariOptions.CAPABILITY,
                    safariOptions);

            // deleteCookies();
            driver = new EventFiringWebDriver(new SafariDriver());

            ThreadDriver.set(driver);
            // driver.manage().window().setSize(new Dimension(1024, 850));
            getDriver().manage().timeouts().implicitlyWait(3,
                    TimeUnit.SECONDS);
            wait = new WebDriverWait(driver, 30);
        }

The configuration tasks (deprecated, use target instead) comes from the plugin maven-antrun-plugin.

So it can't be used in the plugin maven-failsafe-plugin as in your first example.

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.

It seems I'm using Cucumber with Serenity and the Cucumber team is not currently supporting JUnit TestRules for philosophical reasons. Here's hoping they change their mind :)

See https://github.com/cucumber/cucumber-jvm/issues/894