'Test outcome unavailable' in Serenity 3.6.12 + cucumber7 + junit5

[p-nikolaichik]

StepEventBus.getParallelEventBus().getBaseStepListener().getCurrentTestOutcome() is empty in net.serenitybdd.core.webdriver.driverproviders.RemoteDriverProvider

@wakaleo could you confirm it was fixed or related to ticket #3037

[wakaleo]

This is a known issue related to the way parallel execution works - we are looking into seeing if a solution is possible.

[wakaleo]

Fixed in 3.6.22

[p-nikolaichik]

Hi, @wakaleo , could you check please
it is reproduced for serenity.version - 3.6.22
net.thucydides.core.steps.StepEventBus#getBaseStepListener - CurrentListener is null

    <serenity.version>3.6.22</serenity.version>
    <junit.platform.version>1.9.2</junit.platform.version>
    <cucumber.junit.platform.engine.version>7.11.2</cucumber.junit.platform.engine.version>
    <junit.jupiter.migration.support>5.0.0-M4</junit.jupiter.migration.support>
    <dependency>
        <groupId>net.serenity-bdd</groupId>
        <artifactId>serenity-cucumber</artifactId>
        <version>${serenity.version}</version>
    </dependency>
    <dependency>
        <groupId>net.serenity-bdd</groupId>
        <artifactId>serenity-junit5</artifactId>
        <version>${serenity.version}</version>
    </dependency>
    <dependency>
        <groupId>net.serenity-bdd</groupId>
        <artifactId>serenity-rest-assured</artifactId>
        <version>${serenity.version}</version>
    </dependency>
    <dependency>
        <groupId>io.cucumber</groupId>
        <artifactId>cucumber-junit-platform-engine</artifactId>
        <version>${cucumber.junit.platform.engine.version}</version>
    </dependency>
    <dependency>
        <groupId>org.junit.platform</groupId>
        <artifactId>junit-platform-suite</artifactId>
        <version>${junit.platform.version}</version>
    </dependency>
    <dependency>
        <groupId>org.junit.jupiter</groupId>
        <artifactId>junit-jupiter-migration-support</artifactId>
        <version>${junit.jupiter.migration.support}</version>
    </dependency>

cucumber.execution.parallel.enabled=true
cucumber.execution.parallel.config.strategy=fixed
cucumber.execution.parallel.config.fixed.parallelism=60
cucumber.execution.parallel.config.fixed.max-pool-size=60
cucumber.filter.tags=not @Skip and not @Manual

[wakaleo]

That sounds like a different issue. Have you defined the cucumber.plugin property?

cucumber.execution.parallel.enabled=true
cucumber.execution.parallel.config.strategy=fixed
cucumber.execution.parallel.config.fixed.parallelism=4
cucumber.execution.parallel.config.fixed.max-pool-size=4
cucumber.plugin=io.cucumber.core.plugin.SerenityReporterParallel

[p-nikolaichik]

oh, yes, thanks @wakaleo , I lost this line: cucumber.plugin=io.cucumber.core.plugin.SerenityReporterParallel
nevertheless it seems like first issue is not fixed:

[wakaleo]

That's the nature of the parallel execution - the TestOutcome object isn't available until the end of the test.

[p-nikolaichik]

I thought interface BeforeAWebdriverScenario should have this scenario info, otherwise how can I get scenario info to see it in runtime (in selenoid UI)
@wakaleo

[wakaleo]

I thought interface BeforeAWebdriverScenario should have this scenario info, otherwise how can I get scenario info to see it in runtime (in selenoid UI) @wakaleo

In the context of parallel execution, we do not have this information before the scenario starts, only at the end. There isn't a lot we can do about this unfortunately.