ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manish Khettry" <>
Subject RE: junit behavior in ant 1.5 vs 1.3
Date Fri, 21 Feb 2003 17:39:58 GMT

In response to the XML output-- what if the XML output of the test
itself contains a CDATA section? We keep getting parse exceptions from
the junitreport task.


-----Original Message-----
From: Stefan Bodewig []
Sent: Thursday, February 20, 2003 11:35 PM
Subject: Re: junit behavior in ant 1.5 vs 1.3

On Thu, 20 Feb 2003, Manish Khettry <> wrote:

> 1. The standard output and error of the tests now goes to the
> outfile instead of standard output.

Well, really in addition to standard output if you use the
withOutAndErr value for the printsummary attribute.

> This causes problems for us because we use an xml formatter and some
> of our output is XML itself.

The output is supposed to be wrapped into a CDATA section in 1.5, do
you see anything different?

> Since the stdout is sent to a file and the test timesout after a
> while, I can't look at the stdout anymore to see how far the test
> progressed.

see above.

> 2. Some of our multithreaded tests seem to hang. It looks like the
> threads created by the test never seem to run.

This shouldn't have changed between 1.3 and 1.5.x.

> 3. When a test suite times out, the output file has no data. This
> causes junitreport to not even generate information about this
> test.

It wouldn't have any in 1.3 either:

will be fixed in 1.5.2 due to be released Real Soon Now(tm).


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message