Great stuff!!! I've added it to my Ant wiki page:

http://www.thecrumb.com/wiki/Ant

thanks for the kudos, jim ... i'm bummed i missed your ant preso at cfmeetup! i heard it rocked ...

bill

dude... that's what the archives are for!

I'm setting up a time next week to show it to all the people i work with.

Hi!

I've been using cfunit for testing. Was playing with mxunit today and found it really nice.

I quite like the way one can use Ant to automate testing with mxunit.

But I can't find information on one aspect. In cfunit, one can setup a builder in Eclipse to automatically run test as you save the test files (http://cfunit.sourceforge.net/help-ant.php_.

Is there a way in mxunit to do the same? I found documentation on the mxunit ant task, but that seems to output information to a directory rather than print it out in the console.

Thanks

Indy

Hi Indy,

Thanks for the kind words! This might also be a good topic for the mxunit google group (http://groups.google.com/group/mxunit). But until then, this is what I would do:

The MXUnit Ant task can just print info to the console only and not generate any files. Just omit the outputdir attribute in the task definition; e.g., <mxunittask server="localhost" ... >

As for configuring Eclipse to run your Ant build file on save, I would imagine that the same directions provided by cfunit would apply to mxunit, as that is really just calling Ant on an Eclipse save event, I think.

Personally, I do not do that because I do frequent saves and my test directories get pretty big. So, I opt to run my tests when I'm ready to commit to the repo or deploy, and not when saving changes to disk. But that's just me ...

hth,
bill

Thanks Bill. What you suggest works. I had create a build.xml that contained the right tasks.

But you are quite right about why running all tests after save is a bit redundant. Now that I can individually run my tests by double-clicking them in the mxunit view, there is really no need to run all tests on each save.


Thanks for your quick response.