I think HTMLUnit is more powerfull. I agree that HtmlUnit is more verbose,
but you allways can write util methods to avoid that.
You can replace:
HtmlSubmitInput button = (HtmlSubmitInput)form.getInputByName("submitbutton");
HtmlPage page2 = (HtmlPage)button.click();
With:
HtmlPage page2 = HtmlUnitUtils.click("submitbutton");
You will always work with those Utility Methods and when you need some lower
level feature, like js, you use the verbose mode. Then you get the best of
both worlds.
On 7/25/05, Kevin Menard <[EMAIL PROTECTED]> wrote:
>
> Well, I hope this doesn't turn out as bad as hibernate VS
> cayenne ;-) I'm looking into unit testing my webapp and I'm trying
> to decide between these two. htmlunit seems to be more full-
> featured, but also way more verbose (looks like a lot of casting).
> jwebunit seems simpler to use, but lacks stuff such as JS handling
> (is this all that useful anyway?).
>
> Other than that, the only thing I've noticed is that jwebunit is
> about 25% the size of htmlunit and that the former hasn't had a
> release in over a year. Both of these observations really mean
> little though.
>
> Does anyone happen to have experience with these? Is one better
> suited for Tapestry development than the other? I realize that to a
> certain degree, personal preference for APIs plays a role, so to help
> out in those regards, I'm a Tapestry + Cayenne guy.
>
> Any info is greatly appreciated.
>
> Thanks,
> Kevin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
