Regarding the flowscript unit tests, what I wrote was a small unit testing framework for testing the Java API extensions that I ported from Groovy to Javascript, and not flowscript per se. You could probably adopt it or another more featured Javascript unit test framework to test flowscript, however, but it would take some work.

Don

Mark Lowe wrote:
Sorry if this sound stupid, I cant find the url that svn requires to
checkout shale et al. I saw that someone mentioned flowscript unit
testing, I'm working on a cocoon project and I'd like to see if
there's a way of testing the flowscripts we have.

Mark


On Mon, 21 Feb 2005 11:28:04 -0800, Don Brown <[EMAIL PROTECTED]> wrote:

Martin Cooper wrote:
<snip />

OK, I've created a build subproject, with trunk / tags / branches,
added it to 'current', and also added it to the following subprojects:
apps, bsf, core, el, faces, taglib, tiles. I have *not* added it to:
flow, sandbox, shale. Certainly shale uses a separate build system,
but should I go ahead and add it to flow and sandbox?

Sure, flow's build was copied right from bsf. Flow does have a custom run-tests Ant task which uses a homegrown Javascript unit testing framework. It also has two other tasks for building the two example applications. I believe Maven can use Ant tasks, but I have no idea how.

Thanks for the hard work.

Don


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to