IssueHuntDo you want to work on this issue?
You can request for a bounty in order to promote it!
New tests don't start until set of running tests are finished (serenity + junit5 + cucumber7) #3202
p-nikolaichik posted onGitHub
š What did you see?
New tests don't start until set of running tests are finished. I start 1000 scenarios in 50 threads in parallel by scenarios and I noticed that time of execution is 4 hour (for comparison if I run the same suite of tests using jvm parallel plugin in parallel by feature files then total time is 1 hour). I built graphs and saw that new tests are not started even if previous are finished. It means that the threads are just idle waiting for the rest of the tests instead of starting new ones. I created two the similar simple test projects for comparison. First with serenity, second with with poor selenium and web driver manager. Project with simple selenium doesn't have such issue. See following graphs.
ā What did you expect to see?
If test is finished new test is started immediately without waiting for other tests finish
junit-platform.properties:
cucumber.execution.parallel.enabled=true
cucumber.execution.parallel.config.strategy=fixed
cucumber.execution.parallel.config.fixed.parallelism=50
cucumber.execution.parallel.config.fixed.max-pool-size=50
cucumber.plugin=io.cucumber.core.plugin.SerenityReporterParallel
cucumber.filter.tags=not @Skip and not @Manual <serenity.version>3.6.12</serenity.version>
<junit.platform.version>1.9.3</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>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>
<dependency>
<groupId>net.serenity-bdd</groupId>
<artifactId>serenity-rest-assured</artifactId>
<version>${serenity.version}</version>
</dependency>Environment: Reproduced with Serenity 3.6.12/3.9.7, junit4/5, cucumber7, java 11/17 https://github.com/p-nikolaichik/serenity-cucumber-junit5
Serenity
Selenium with web driver manager
@wakaleo Maybe I missed some necessary config parameter to run tests in parallel?
