FYI I've started a javascript plugin project as part of maven Mojo. It allready support running jsunit tests :
http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools You can look at javascript-maven-plugin JsUnitMojo, that runs a customized TestCase with a shared jsUnit server to avoid the server-per-test issue you noticed. You will not be able to run the plugin as many dependencies are not (yet) available in central repo. You can look at the src/it projects on how to configure and use the plugin for jsunit tests. Could you give me an example of the test result generated from jsunit result ? This part of the plugin is far perfectible, and I would welcome contribution ;-) Nico. 2007/10/22, Insitu <[EMAIL PROTECTED]>: > > Hello, > I am working on integrating jsunit (http://www.jsunit.net) into > maven. I would like to share some thoughts and request some advices > avout the best way to do that integration. > > Right now, I have a sample (maven) project that executes jsunit tests > from maven and generates reports. What I did is: > - modify jsunit java server test cases to generate JUnit test results > from jsunit test results: That way javascript unit tests results > and error gets integrated seamlessly into surefire's reports > - package the java server as an artifact > - encapsulates all tests in a single JUnit tests cases that > configures things and laucn jsunit's StandaloneTest class > > Some problems are: > - test pages contains hardwired and absolute references to everything > (ie. scripts and jsunti base directory) which is BAD ! > - you need to install jsunit somewhere locally > - you need to modify and track files by hand outside of the scope of > the project > - test server is started once for each test execution or event each > JUnit test class execution which can be a performance bottleneck > for large and/or deep projects > > What I want to do is: > 1. package jsunit runner and support files as a jar or zip > 2. create a plugin tbound to process-test-sources that would unpack > the jsunit site in target/jsunit-runner > 3. configure generically test server/runners to have > target/jsunit-runner as their root site. This implies that > javascript source files, test files and test pages be moved to > this directory too... > > Ideally, I would rather serve everything from a servlet launched > through jetty with the adequate maven plugin but this would require > heavy changes to jsunit java server code. Or may be not... > > Comments and ideas are welcomed, > > regards, > -- > OQube < software engineering \ génie logiciel > > Arnaud Bailly, Dr. > \web> http://www.oqube.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
