My pragmatic answer is just use something, and just actually test. Which tool you use is almost a technical detail.
I used HttpUnit on my current project, but it's not perfect. It does enough of what I want, that I was able to code up a couple of helper objects and get most of the rest of my needs met. I haven't used HtmlUnit, but I'd expect that it would also fall short in certain areas and that with a couple of helper objects it could be made quite usable. :-) Also consider the level of abstraction that you want to work at. HttpUnit, as it's name suggests, is very close to the HTTP, perhaps HtmlUnit hides more of that. JWebUnit hides even more, I've heard. To paraphrase Tolkien ... "Go not to the Struts Mailing List, for they shall say both yes and no". :-) Simon >-----Original Message----- >From: Mike Duffy [mailto:[EMAIL PROTECTED] >Sent: Thursday, May 06, 2004 2:58 PM >To: Struts Users Mailing List >Subject: [OT: HTTPUNIT vs HTMLUNIT] > > >Does any one have a recommendation on HTTPUnit vs HTMLUnit? > >http://httpunit.sourceforge.net > >http://htmlunit.sourceforge.net > >Thx. > >Mike > > > > >__________________________________ >Do you Yahoo!? >Win a $20,000 Career Makeover at Yahoo! HotJobs >http://hotjobs.sweepstakes.yahoo.com/careermakeover > >--------------------------------------------------------------------- >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]
