[CURATOR-61] Use a new surefire process per test class #582
Description
Currently, we are using a single surefire process per test suite.
With this setup we only see the test results only when all tests of the module have finished.
In many cases, it is useful to get the results right after the test class is complete.
Why? Because, some modules take a really long time to run and some times it hard to tell if particular has hung.
If we use fork mode "always" / forkCount=1 reuseForks=false each test class will use its own surefire process and we will get the results on screen for each test class.
Originally reported by iocanel, imported from: Use a new surefire process per test class
- assignee: iocanel
- status: Resolved
- priority: Minor
- resolution: Fixed
- resolved: 2013-10-04T20:36:54+01:00
- imported: 2025-01-21