Ahhh HtmlUnit and HttpUnit look like awesome tools. And integrating them into the cargo API is a good idea as well. Much thanks Wendy!
-----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, June 05, 2006 7:10 PM To: Maven Users List Subject: Re: Question on how users code/test their war applications On 6/5/06, William Kinney <[EMAIL PROTECTED]> wrote: > I was just curious how other maven 2 users currently go through coding/testing war applications on i.e. tomcat or jboss. Do you just code, package, deploy to local and UI test? Do you usually do exploded war? Or do you heavily rely on JUnit? Or do you have a remote test box you remote deploy to every time? Or do you manually mv/copy paste? Trying to get an idea of how best to normalize war application testing for a project... If you just want to start the app and click through to make sure it works, you can configure either the Cargo (which can start many different containers) or Jetty plugin. For in-container testing, one option is a combination of Cargo's Java API and HtmlUnit (or HttpUnit) tests. The JUnit TestSetup class uses Cargo to start the container, then the tests are run, then the container is stopped. We're doing this to make sure the Struts example apps deploy and start. An extension of this might be using Canoo WebTest so you don't have to write the tests in Java. Another option is Selenium, which allows you to record tests and run them later. I haven't had a chance to try this yet, but it's here: http://www.openqa.org/selenium-ide/ This is obviously not an exhaustive list, just some things I've either used or have on my list to take a look at. :) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
