Hi
Maybe you could set the "timeout" property of the task, so timeout
will appears in junit reports as cause for test failure.
Regards
Emmanuel
--
View this message in context:
http://ant.1045680.n5.nabble.com/junit-ant-task-tp3233265p3243947.html
Sent from the Ant - Users mailing list archiv
Dean
if its surefire then look in ${project.folder}/target/surefire-reports you
should see
${GroupId}.${ArtifactId}.txt and
${GroupId}.${ArtifactId}.xml
search for
Failures: 1
Errors: 1
Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de
-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org]
Sent: Monday, August 23, 2010 9:20 AM
To: user@ant.apache.org
Subject: Re: junit ant task test listeners
On 2010-08-23, Chip McCormick wrote:
> Does anyone know how to add a test listener to an ant junit t
On 2010-08-23, Chip McCormick wrote:
> Does anyone know how to add a test listener to an ant junit task,
> without having to create a custom task?
> We are attempting to add a test listener to a junit ant task to do
> custom logging after each test class in a batch completes.
Ant's formatters ar
> I am sure that most of you have seen this message com across
> the list before. I am trying to use junit with ant. I want
> to be able to have the junit.jar file reside somewhere else
> than in the ANT_HOME/lib directory. I have searched the web
> for ideas about how to solve this problem
I think I have another workaround. [It is kinda related to Mark Hansen's
approach in that it uses another class, but the class is used differently
here (I think). I only make a call once, instead of each time in setup().]
Here it is: If inside a test case method in my TestCase class I instanti
setup() code into the TestFoo
constructor instead? That way, you don't need to do the stuff in
teardown(), right?
Or am I missing something?
Oski
From: Mark Hansen <[EMAIL PROTECTED]>
Reply-To: "Ant Users List"
To: Ant Users List
Subject: RE: JUnit, ANT, log4j, System.out is
I ran into this same problem (but in the context of
using Maven). The problem is that JUnit redirects
STDOUT *AFTER* the log4j configuration has taken
place.
If you want your log4j console appender output to go
to the same place that JUnit sends STDOUT, you need to
create the log4j console append
PROTECTED]
Sent: Friday, March 25, 2005 14:49
To: Ant Users List
Subject: Re: JUnit, ANT, log4j, System.out issue
I think this is an explanation of the problem. Log4J ConsoleAppender
descends from WriterAppender (or something similar) and it remembers
System.out (or System.err) values during
I think this is an explanation of the problem. Log4J ConsoleAppender
descends from WriterAppender (or something similar) and it remembers
System.out (or System.err) values during initialization. If later
anybody changes System.out (or .err), Log4J does not notice it. I would
suggest writing you
Anybody? Anybody? Bueller?
Seriously, I'd at least appreciate any insight/speculation as to where the
problem might be. If nobody knows exactly what is going on I'll have to look
at the source and it would be nice to have some opinions about where to start
(e.g. ANT vs JUnit, specific modules/
11 matches
Mail list logo
