In CI we currently split up our tests by module, and run those completely independently, but each module runs serially. It would be beneficial to reduce our test time (particularly for PRB and release) by running tests in parallel within a github worker. This would also be beneficial for inner loops for developers.
JUnit 6.1 introduced a new execution strategy that does not depend a ForkJoinPool, which means that we should be able to run with multiple test worker threads.
Given that a lot of our tests interact with shared state (particularly FDB and thread pools), some work will be needed to get all tests to pass successfully, reliably with the parallelism enabled.
In CI we currently split up our tests by module, and run those completely independently, but each module runs serially. It would be beneficial to reduce our test time (particularly for PRB and release) by running tests in parallel within a github worker. This would also be beneficial for inner loops for developers.
JUnit 6.1 introduced a new execution strategy that does not depend a ForkJoinPool, which means that we should be able to run with multiple test worker threads.
Given that a lot of our tests interact with shared state (particularly FDB and thread pools), some work will be needed to get all tests to pass successfully, reliably with the parallelism enabled.