Bug 35073

Summary:	JUnit test runner outputs to stdout on failures, instead of relying on formatter
Product:	Ant	Reporter:	Alexander Staubo <apache.org>
Component:	Optional Tasks	Assignee:	Ant Notifications List <notifications>
Status:	RESOLVED FIXED
Severity:	normal	Keywords:	PatchAvailable
Priority:	P2
Version:	1.6.4
Target Milestone:	1.8.0
Hardware:	All
OS:	All
Attachments:	Patch to remove output

Description Alexander Staubo 2005-05-26 00:24:26 UTC

On test failures, the JUnit test runner outputs lines such as this:

TEST com.example.Foo FAILED

It does this regardless of which formatter has been set. There's no way to
disable the behaviour.

This means that when you make an effort to plug in a formatter which produces
good-looking output, you also get the "TEST" stuff cluttering your output.

Comment 1 Alexander Staubo 2005-05-26 00:25:53 UTC

Created attachment 15173 [details]
Patch to remove output

Comment 2 Stefan Bodewig 2009-08-18 06:55:56 UTC

this is the branch where JUnit is running in forked mode, running multiple tests in the same forked VM and doesn't halt on failures/errors.

The line corresponds to a log statement in JUnitTask that at the ERR level that cannot be suppressed either.  Without the lines in JUnitTestRunner you'd lose any indication of which test failed in Ant's log.

We should either suppress both log messages or neither, which means we need a new option, sigh.

logfailedtests it is, svn revision 805415