Re: Ant test framework

[di...@multitask.com.au]

This is part of an email conversation between Conor and myself about
getting the build file test framework available as another deliverable of
ant.

In Maven, we've written several project specific tasks that need to be
tested on a regular basis, and rather than subsume the source code from
Ant, we'd much prefer the 'Ant Test Framework' to be available as a jar
file so that other projects can specify it as a test dependency, and use
it.

So the proposal is that for Ant 1.6 and beyond the test classes needed to
test build files be packaged up as another jar and made a deliverable like
the optional jar is.

Votes: +1/-1/+0/-0?

I'm willing to make a new build file for ant to build the test framework
and package it as a jar (i.e. +1 from a non-committer).
--
dIon Gillard, Multitask Consulting
Work:      http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
----- Forwarded by dIon Gillard/Multitask Consulting/AU on 05/28/02 11:39
AM -----



dion@multitask.com.au wrote:
> So what do you think I should do?

Let's make it happen in Ant. That would be a start :-) There is already
some impetus so adding your voice as a task developer requesting the
feature would help move it along.

> I don't want to copy it into Maven's
> source tree and maintain it there,

No - that would suck - enough of that going on already.

You've convinced me that this should be part of the Ant deliverable.

> like we're doing with the Ant target,
> but writing ant tasks without testing them is damn stupid.

We should talk about that a bit more - this is to set the refs in the
parent project?

>
> I know - don't write tasks :)

Writing tasks is a good thing :-)

>
> I'll check out the dependencies and see what I can do....

I've had a quick look just now. It seems pretty well self contained
(inner classes) External deps will be junit.jar and ant.jar

Conor





--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Ant test framework

[Stefan Bodewig <bo...@apache.org>]

On Mon, 27 May 2002, Steve Loughran <st...@iseran.com> wrote:

> I think Mageshe's concept, which I was happy with, was to have a
> separate jar, number it ant-test-framework1.5.jar, or the like, and
> make *no* guarantees about forward/backwards compatibility.

In the 1.5 branch I've added targets to jar up the things that I
considered useful for third party tests as well as to creat javadocs
for them.  It would be trivial to add them to the binary distribution.

Stefan

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Ant test framework

[Steve Loughran <st...@iseran.com>]

----- Original Message -----
From: "Conor MacNeill" <co...@cortexebusiness.com.au>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Monday, May 27, 2002 7:03 PM
Subject: Re: Ant test framework


>
>
> dion@multitask.com.au wrote:
> > This is part of an email conversation between Conor and myself about
> > getting the build file test framework available as another deliverable
of
> > ant.
> >
> > In Maven, we've written several project specific tasks that need to be
> > tested on a regular basis, and rather than subsume the source code from
> > Ant, we'd much prefer the 'Ant Test Framework' to be available as a jar
> > file so that other projects can specify it as a test dependency, and use
> > it.
> >
> > So the proposal is that for Ant 1.6 and beyond the test classes needed
to
> > test build files be packaged up as another jar and made a deliverable
like
> > the optional jar is.
> >
> > Votes: +1/-1/+0/-0?
> >
> > I'm willing to make a new build file for ant to build the test framework
> > and package it as a jar (i.e. +1 from a non-committer).
>
> As I said, Steve has been looking at this. I can't remember the latest
> thinking. I've looked a bit further just now and I think that perhaps
> the easiest thing is just to move BuildFileTest into the main source
> tree (and hence ant.jar) without moving it in its package namespace. The
> Ant tests would continue to function as is and task developers would not
> have to copy and paste code to access test facilities.

I think Mageshe's concept, which I was happy with, was to have a separate
jar, number it ant-test-framework1.5.jar, or the like, and make *no*
guarantees about forward/backwards compatibility.

If we publish the tests as part of the core API, then it is frozen for
eternal support.

seems to me that there is something odd about the fact that we have to code
our build file tests in java. Surely we should be able to do a lot of them
(all the ones where we make assertions about the state of properties, or
expect assertions), using a more declarative XML style...

steve





--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Ant test framework

[Conor MacNeill <co...@cortexebusiness.com.au>]

dion@multitask.com.au wrote:
> This is part of an email conversation between Conor and myself about
> getting the build file test framework available as another deliverable of
> ant.
> 
> In Maven, we've written several project specific tasks that need to be
> tested on a regular basis, and rather than subsume the source code from
> Ant, we'd much prefer the 'Ant Test Framework' to be available as a jar
> file so that other projects can specify it as a test dependency, and use
> it.
> 
> So the proposal is that for Ant 1.6 and beyond the test classes needed to
> test build files be packaged up as another jar and made a deliverable like
> the optional jar is.
> 
> Votes: +1/-1/+0/-0?
> 
> I'm willing to make a new build file for ant to build the test framework
> and package it as a jar (i.e. +1 from a non-committer).

As I said, Steve has been looking at this. I can't remember the latest 
thinking. I've looked a bit further just now and I think that perhaps 
the easiest thing is just to move BuildFileTest into the main source 
tree (and hence ant.jar) without moving it in its package namespace. The 
Ant tests would continue to function as is and task developers would not 
have to copy and paste code to access test facilities.

Thoughts?

Conor



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Ant test framework

[Erik Meade <em...@geekfarm.org>]

> -----Original Message-----
> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
> Sent: Monday, May 27, 2002 8:44 PM
> To: ant-dev@jakarta.apache.org
> Subject: Re: Ant test framework
>
>
> In Maven, we've written several project specific tasks that need to be
> tested on a regular basis, and rather than subsume the source code from
> Ant, we'd much prefer the 'Ant Test Framework' to be available as a jar
> file so that other projects can specify it as a test dependency, and use
> it.
>
> So the proposal is that for Ant 1.6 and beyond the test classes needed to
> test build files be packaged up as another jar and made a deliverable like
> the optional jar is.
>
> Votes: +1/-1/+0/-0?
>

+1

It should be easy to write tests.  A few weeks ago I was working with a
client
on a Clear Case ant task, because of firewall issues we couldn't get the
testing
stuff out of CVS, the result was we hacked it out, but don't want to submit
it
without tests.

Erik Meade
http://junit.org
emeade@objectmentor.com


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>