How cucumber.execution.parallel.enabled works with cucumber.execution.order?

[TrueJacobG]

Requirements:

cucumber.execution.parallel.enabled=true
cucumber.execution.parallel.config.strategy=fixed
cucumber.execution.parallel.config.fixed.max-pool-size=5

cucumber.execution.order=lexical

platform: JUnit 5

---

I believe we can assume that tests will start in alphabetical order on each thread. However, while we cannot assume that tests will both start and finish in alphabetical order overall, we can assume that if we examine all tests performed on, lets say, thread 1, they were started in alphabetical order, right?

[mpkorstanje]

At the moment configuring the execution order isn't supported by the Cucumber JUnit Platform Engine. You can see that the property isn't listed in the supported configuration properties.

This may become supported once the next version of JUnit is released and I can finish #2835.

The default ordering is lexical by feature file uri.

The Cucumber JUnit Platform Engine uses the JUnit Platform for parallel execution and the current implementation uses a ForkJoinPool. This pool utilized work stealing. As such no guarantees can be made about ordering or even the thread on which a scenario or example is executed.

The exception to this are the cucumber.execution.execution-mode.feature property which makes it possible to run all scenarios and examples in a feature on the same thread.

Likewise using exclusive resources has a similar effect. Though mostly as a side effect of the current JUnit Platform.

There is also the more generic possibility in the JUnit Platform to configure tests to run on the same thread as their sublings, but that hasn't been implemented in Cucumber yet

Edit: oops, wrong button

[TrueJacobG]

Thank you for the information! 🥇