[mwringe]

Do we want the full coverage of the things that cactus does? even things like custom tasks to run tests?

[ssilvert]

"mwringe" wrote:
Do we want the full coverage of the things that cactus does? even things like custom tasks to run tests?

Since this will be a complete rewrite, I don't think we have to stick to the exact same tasks offered by cactify.

However, the overall goals are basically the same. If I have a WAR, want to be able to run JSFUnit tests against it. So, I need a task or tasks that will create a version of the WAR that bundles the needed libraries and modifies my web.xml. It would also bundle cactus-report.xsl and cactus.properties.

In addition, I need to be able run the tests in an automated build. Maybe this can be done with a combination of an ant cargo task and an ant junit task. That's basically how it is done with Maven today. If this can be made easier with a JSFUnit ant task then that's fine, but we at least need a working example for ant that we can document.

At the end of the day, we need to be able to show how someone can use ant to say:

"ant buildjsfunitwar" for building without running

and

"ant runjsfunitwar" for automated testing.

Stan