You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Ioannis Canellos (JIRA)" <ji...@apache.org> on 2013/10/04 21:22:47 UTC
[jira] [Created] (CURATOR-61) Use a new surefire process per test
class
Ioannis Canellos created CURATOR-61:
---------------------------------------
Summary: Use a new surefire process per test class
Key: CURATOR-61
URL: https://issues.apache.org/jira/browse/CURATOR-61
Project: Apache Curator
Issue Type: Improvement
Components: Tests
Reporter: Ioannis Canellos
Assignee: Ioannis Canellos
Priority: Minor
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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)