curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ioannis Canellos (JIRA)" <>
Subject [jira] [Resolved] (CURATOR-61) Use a new surefire process per test class
Date Fri, 04 Oct 2013 19:37:44 GMT


Ioannis Canellos resolved CURATOR-61.

       Resolution: Fixed
    Fix Version/s: next-release

> Use a new surefire process per test class
> -----------------------------------------
>                 Key: CURATOR-61
>                 URL:
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Tests
>            Reporter: Ioannis Canellos
>            Assignee: Ioannis Canellos
>            Priority: Minor
>             Fix For: next-release
> 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

View raw message