Mailing-List: contact commits-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@buildr.apache.org
Message-ID: <17778228.35971291900263086.JavaMail.jira@thor>
Date: Thu, 9 Dec 2010 08:11:03 -0500 (EST)
From: "Tammo van Lessen (JIRA)" <jira@apache.org>
To: buildr-commits@incubator.apache.org
Subject: [jira] Created: (BUILDR-561) Test framework should provide a
 forkMode option
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Test framework should provide a forkMode option
-----------------------------------------------

                 Key: BUILDR-561
                 URL: https://issues.apache.org/jira/browse/BUILDR-561
             Project: Buildr
          Issue Type: Improvement
          Components: Test frameworks
            Reporter: Tammo van Lessen
             Fix For: Wish List


When running large builds with complex test cases (like integration tests), it is often required to adjust the fork mode. Maven's surefire plugin for instance knows 3 fork modes: "never", "once", "always".

It would be great to support these 3 modes as first class citizen. If a fork mode is not supported by buildr a meaningful error can be thrown. E.g. currently buildr's testng wrapper only supports "once".

In general it would be great if test wrappers could support all modes and, if "always" is not supported directly by the framework, emulate the behavior. This might be tricky as reports need to be merged if test are run one-by-one.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.