Yeah, that would suit my purposes. Seems like the first line is the only one
likely to contain a space before the word " more" anyway, aside from the line
we want to strip.
Bob
On Aug 5, 2011, at 8:40 AM, Stefan Bodewig wrote:
> On 2011-08-04, Robert E. Billings III wrote:
>
>> OK, I'll fil
On 2011-08-04, Robert E. Billings III wrote:
> OK, I'll fill out a bugzilla report. Thanks for verifying! :)
Would it be enough if we simply started filtering after the first line
of the stack trace? That fix would be easiest to implement.
Stefan
--
OK, I'll fill out a bugzilla report. Thanks for verifying! :)
Bob
On Thu, Aug 4, 2011 at 11:05 AM, Stefan Bodewig wrote:
> On 2011-07-28, Bob Billings wrote:
>
> > However, the Ant junit XML formatter strips off the first line with
> > the failure message in any test failure where the failure
On 2011-07-28, Bob Billings wrote:
> However, the Ant junit XML formatter strips off the first line with
> the failure message in any test failure where the failure message
> contains the word " more", resulting in just the "at " line
> remaining, which is what shows up in CruiseControl's emai
That'd be very handy sometimes!
+1
Juan Pablo Lis wrote:
Hello All,
I'm having a problem while running junit tasks, when the test is large.
I'm getting an out of memory exception, but I notice that the formatter
(XML) is not flushing the file while it is running, it writes the whole file
at t
Tim Visher wrote:
Wow... let me feel sheepish for a bit as I blithely mentioned the
acquisition of Ant in Action to its author (sometimes, reading
signatures is helpful)...
I took it at a complement. If you'd said it hadn't helped, then I'd be
worried
I suppose that means that help from
Wow... let me feel sheepish for a bit as I blithely mentioned the
acquisition of Ant in Action to its author (sometimes, reading
signatures is helpful)... I suppose that means that help from that
book may be a little bit of a long shot, or was the junit task covered
somewhat in depth in your book,
@Steve: I'm not too sure I understand what you're talking about. The
junit task that ant 1.7 comes with works with junit 4. All of the
tests I have written are 'pure' junit 4 tests and I've got the junit
task running fine. I just think there needs to be better
documentation written for the junit
Tim Visher wrote:
Thanks, I actually had done that query already and couldn't come up
with anything particularly good. Most of it is outdated (JUnit 3, Ant
1.3, 1.5, etc.) and I don't really have time to translate them with
almost 0 knowledge of ant. I was hoping for a little bit more
focussed
Thanks, I actually had done that query already and couldn't come up
with anything particularly good. Most of it is outdated (JUnit 3, Ant
1.3, 1.5, etc.) and I don't really have time to translate them with
almost 0 knowledge of ant. I was hoping for a little bit more
focussed help.
However, ther
check out this...
http://www.google.fr/search?source=ig&hl=en&rlz=&=&q=junit+and+ant+tutorials
Hello everyone,
I'm struggling to understand the junit task. I was wondering if
anyone knew of a good tutorial or article that is current (junit 4,
ant 1.7) that is perhaps slightly better than the ju
27;t tried it yet, I was a little wary of fork for some unfounded
fear of runaway processes or something. But it worked, so it's all good.
Thanks!
-Original Message-
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Monday, September 10, 2007 6:36 AM
To: Ant Users List
Subject:
Preston, Brian wrote:
Is there a common 'gotcha' with running the junit task and classpaths?
Because I'm having a problem where my tests run against the database, so
they need the drivers on the classpath, and they're not being found.
Here's the error :
java.sql.SQLException: No suitable drive
Peter,
thanks for your response. the simple solution was to add the
junit.jar to my ant lib/ dir. duh. thanks for 'reminding' me of the
verbose feature. i'll try to be a bit more diligent in the future. ;)
andy
On 1/29/07, Peter Reilly <[EMAIL PROTECTED]> wrote:
try with ant -verbose.
Th
try with ant -verbose.
This problem can happen with having old versions
of ant in the classpath of the forked junit task.
In this case the contents of lib.path should be looked
at. (common causes would be jars that have embedded
ant classes - fo example weblogic.jar and jrun.jar)
In the current
On Fri, 27 Jan 2006, Carlton Brown <[EMAIL PROTECTED]>
wrote:
> The ant task seems to create zero-length output files for a
> few of my unit test classes.
Which version of Ant are you using? There have been some problems
with tests running into timeouts or crashing the VM, but they are
supposed
On 1/27/06, Brown, Carlton <[EMAIL PROTECTED]> wrote:
> The ant task seems to create zero-length output files for a few
> of my unit test classes. It does so without reporting any errors but
> of course of course chokes on them complaining about
> premature EOF.
> Does anyone have any suggestio
> >That's given your basedir as a pathelement - how about giving it the
> >"testing" directory instead? Isn't that the base of the testing classes?
>
> But I think that is correct.
> The base dir is, say, xxx. The testing dir sits below this with tests that
> are in the testing package.
> So sitti
Phew, got there in the endthanks for the help.
cheers
Andy
_
Be the first to hear what's new at MSN - sign up to our free newsletters!
http://www.msn.co.uk/newsletters
---
> >That's given your basedir as a pathelement - how about giving it the
> >"testing" directory instead? Isn't that the base of the
> testing classes?
>
> But I think that is correct.
> The base dir is, say, xxx. The testing dir sits below this
> with tests that are in the testing package.
> So
That's given your basedir as a pathelement - how about giving it the
"testing" directory instead? Isn't that the base of the testing classes?
But I think that is correct.
The base dir is, say, xxx. The testing dir sits below this with tests that
are in the testing package.
So sitting in my x
> > > so it seems the fileset bit works (finds the test) but
> JUnit doesn't
> >have
> > > the classpath.
> >
> >Simply because you didn't provide any ;-)
> >
> >You'd need a nested (within ) with at least your
> >"testing" directory, and any other jar(s) or directory(ies)
> required to
> >run
> so it seems the fileset bit works (finds the test) but JUnit doesn't
have
> the classpath.
Simply because you didn't provide any ;-)
You'd need a nested (within ) with at least your
"testing" directory, and any other jar(s) or directory(ies) required
to run the tests. --DD
At the danger o
>
>
>
>
>
>
>
>
>
>
>
> so it seems the fileset bit works (finds the test) but JUnit doesn't have
> the classpath.
Simply because you didn't provide any ;-)
You'd need a nested (within ) with at least your
"testing" directory, and any other jar(s) or directory
I see you're using the ant-junit.jar file. That is the Ant Task wrapper for
Junit and you shouldn't need to reference it ordinarily. It's there to define
the JUnit task and doesn't include the JUnit core API. You need to include
junit.jar in Ant's CLASSPATH or in the CLASSPATH of an explicit tas
> When i run the ant junit task i get the following error :
Have you looked at the FAQ entry about Junit? See
http://ant.apache.org/faq.html#delegating-classloader
Have you placed your junit jar file (not the Ant one, Junit itself) in
the ant\lib directory?
Jon
Clearswift monitors, controls a
On Sat, 20 Aug 2005, Alan Gutierrez <[EMAIL PROTECTED]> wrote:
> Is there a way to change directory, or can/should I pass in the
> base direcotry using sysproperty?
Yes, has a dir attribute, which only works if you run the task
with fork="true".
Stefan
-
see:
http://issues.apache.org/bugzilla/show_bug.cgi?id=34748
Peter
Conor MacNeill wrote:
Ah, sorry - you are right - no way AFAIK.
Conor
Martin Burger wrote:
Conor MacNeill schrieb am 18.07.2005 13:01:
Look at the element.
Also, for an example, look at Ant's build file.
Ah, sorry - you are right - no way AFAIK.
Conor
Martin Burger wrote:
> Conor MacNeill schrieb am 18.07.2005 13:01:
>
>> Look at the element.
>>
>>
>>
>> Also, for an example, look at Ant's build file.
>>
>
> That executes all test methods defined in $testcase, doesn't?
>
> I looked mea
Conor MacNeill schrieb am 18.07.2005 13:01:
Look at the element.
Also, for an example, look at Ant's build file.
That executes all test methods defined in $testcase, doesn't?
I looked meantime at the source code, I think it is not possible to
execute a single test method. JUnitTask
Martin Burger wrote:
> Hello,
>
> using the JUnit task is it possible to execute a single test _method_?
>
Look at the element.
Also, for an example, look at Ant's build file.
Conor
-
To unsubscribe, e-mail: [EMAIL P
t; http://www.manning-source.com/books/hatcher/hatcher_ch04.pdf (sample
> chapter Testing with JUnit, from Java Development with Ant).
>
> Kajsa Anderson
>
>> -Original Message-
>> From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, February 17,
obably want the first formatter.
...
> -Original Message-
> From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 17, 2005 1:45 PM
> To: Ant Users List
> Subject: RE: JUnit task problem
>
> I though
h Ant).
Kajsa Anderson
> -Original Message-
> From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 17, 2005 1:45 PM
> To: Ant Users List
> Subject: RE: JUnit task problem
>
>
> I thought of that too... I wasn't sure it it was needed or
I thought of that too... I wasn't sure it it was needed or not so I left
it out just to have a slightly simpler class... however, I did try putting
it in and it doesn't make the error go away. I'll leave it in for now
anyway, but that doesn't seem to be it.
--
Frank W. Zammetti
Founder and Chief
I think your test class needs a constructor (inserted below).
> -Original Message-
> From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 17, 2005 11:29 AM
> To: user@ant.apache.org
> Subject: JUnit task problem
>
>
> Hi again... having a bit of problem with my f
Dear Black:
I just love the easy ones
Your test target creates XML output by default unless you tell the formatter
to output to txt
take a look at
http://ant.apache.org/manual/OptionalTasks/junit.html
the output should be
com.mytests.test.*.xml
the output Doesnt really do much good unless you use a
Hi,
I note that you are using httpunit which makes me
consider that your tests try to connect to some
server. If so are you sure the server is running? Your
tests might wait for it.
Could you also try timeout attribute of junit task?
Set it first to some short value to observe what is
happening.
38 matches
Mail list logo
