--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> Hi,
>
> inspired by the creative use of and
> others (mainly
> Matt and Steve) have shown in our tests, the idea of
> AntUnit we had a
> long time ago surfaced in my mind again.
Cool. I'm pretty sure it was some of Steve's tests
that inspired me
At 10:31 AM 4/14/2005, you wrote:
On Thu, 14 Apr 2005, Wascally Wabbit <[EMAIL PROTECTED]>
wrote:
> I have already created such a beast using Ant; the project is
> waiting to to be cleaned up before being posted on Sourceforge
> (at antunit).
Let me see it! 8-)
The implementation is a bit out-of-da
On Thu, 14 Apr 2005, Wascally Wabbit <[EMAIL PROTECTED]>
wrote:
> I have already created such a beast using Ant; the project is
> waiting to to be cleaned up before being posted on Sourceforge
> (at antunit).
Let me see it! 8-)
> What are the chances of you taking a look-see so work isn't
> dupl
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
> >> (1) create an Ant task
> >> (2) run the target named setUp if present
> >> (3) run the target
> >> (4) run the target named tearDown if present
> >
> > (2) mimicks JUnit, but may not be necessary.
>
> Yes, I thought about that but wanted it to
On Thu, 14 Apr 2005, Paul King <[EMAIL PROTECTED]> wrote:
> It would seem reasonable to be able to write tests productively use
> ant build files.
Its main purpose should be to test Ant or Ant tasks. It would be easy
to rewrite larger parts of Ant's own JUnit tests that way - almost
every Unit t
On Thu, 14 Apr 2005, Dominique Devienne <[EMAIL PROTECTED]> wrote:
>> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
>>
>> The other part will be an task, which will take a build
>> file and for each target whose name starts with "test" will
>>
>> (1) create an Ant task
>> (2) run the target nam
Stefan,
I have already created such a beast using Ant; the project is
waiting to to be cleaned up before being posted on Sourceforge
(at antunit). I had planned to get to it before summer's end.
Not to beat my own drum but it does a full JUnitisque framework
in Ant. It has not been released yet so
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
>
> The other part will be an task, which will take a build file
> and for each target whose name starts with "test" will
>
> (1) create an Ant task
> (2) run the target named setUp if present
> (3) run the target
> (4) run the target named tearDo
I would mostly encourage this. It would seem reasonable
to be able to write tests productively use ant build files.
I am not sure how directly tied to ant (vs testing any java
program) you would need to make it to be worthwhile. I would
hope that it could be more generic.
You might want to have a l
Hi,
inspired by the creative use of and others (mainly
Matt and Steve) have shown in our tests, the idea of AntUnit we had a
long time ago surfaced in my mind again.
I've just dumped a little macrodef antlib (and one "real" task,
) into our proposal area. This is only a temporary place
until m
10 matches
Mail list logo
