fslev
fslev
Indeed. Some compact related styles were sacrificed. Compact is good for small screens. However, in a demo session, on a projector, it's quite hard to follow all the details. Pros...
Use a custom parallel execution configuration strategy (don't forget to implement the new getSaturatedPredicate method - Junit 1.9.0) https://github.com/fslev/cucumber-selenium-tutorial/blob/main/src/test/java/io/cucumber/selenium/tutorial/config/FixedParallelExecutionConfigurationStrategy.java junit-platform.properties ``` cucumber.execution.parallel.config.custom.class=io.cucumber.selenium.tutorial.config.FixedParallelExecutionConfigurationStrategy ``` This way, you will always have a...
Use your Appium session(s) inside a static ThreadLocal variable (works perfect when parallelism is enabled) and close it/them within an @AfterAll hook.
All scenarios from same feature file are running in isolation even if only one has the @isolated tag
Sorry for that. They are pushed now. So it seems this is a Junit 5 constraint... In which case, maybe the [documenation](https://github.com/cucumber/cucumber-jvm/tree/main/junit-platform-engine#running-tests-in-isolation) might be adjusted a little bit. That way,...
Also, a new Junit version (5.10.0) will soon be available, which uses saturated thread pool by default: https://junit.org/junit5/docs/snapshot/release-notes/#deprecations-and-breaking-changes-2 Hence, no need for a custom parallel execution configuration strategy anymore, in...