On Thu, 2004-10-14 at 05:12, Stefan Bodewig wrote:
> If there is a way to predict the number of tests before running them,
> we could extend JUnitTest to hold that information and your new
> formatter could capture it in startTestSuite.
junit.swingui.TestRunner uses junit.framework.Test.countTestC
On Thu, 07 Oct 2004, Tom Ball <[EMAIL PROTECTED]> wrote:
> Perhaps the right answer is for JUnitTestRunner to report test
> count, start and end via new methods in the JUnitResultFormatter
> interface,
I don't think the TestRunner actually knows the number of tests before
running them, I may be w
On Thu, 2004-10-07 at 13:17, Dominique Devienne wrote:
> For this reason, JUnitTestRunner has to be as stand-alone as possible,
> and Ant injects just enough of itself classpath-wise so that
> JUnitTestRunner has all it needs, in addition to the user-specified
> classpath.
Sure, that makes sense.
> From: Tom Ball [mailto:[EMAIL PROTECTED]
>
> 1. (Preferred) Log sub-informational messages for these events, which
a
> BuildListener could filter. The problem is that while the JUnitTask
> logs events, its JUnitTestRunner does not (everything goes to stdout
and
> stderr). JUnitTestRunner is c
