I am trying to run my tests in parallel, and I have a use-case different from all others that I have been able to find.
My tests are laid out pretty straight-forward, something like the following: src/test/java/ +-features.areaA | +-SomeStory.java | +-AnotherStory.java | ... +-features.areaB | +-DifferentStory.java | +-OtherStory.java | ... ... The tests are written using serenity-bdd, which is a wrapper for selenium, and the test manager is junit4. Each "area" represents some discreet area of the application under test. Tests within one area cannot run in parallel as they would clobber the data they are using. However, tests between different areas can certainly run in parallel as there are no collisions. I tried to configure my maven-failsafe-plugin according to the documentation (https://maven.apache.org/surefire/maven-failsafe-plugin/examples/fork-options-and-parallel-execution.html). Using parallel=suites and any one of threadCount=4, threadCountSuites=4, or useUnlimitedThreads=true, results in only one test being run at a time. Is my understanding of "suites" wrong in the context of Failsafe plugin? Is it possible to parallelize tests so that entire packages are fed into VM threads one at a time, but classes within one package run sequentially? ty --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org