[Webtest] Re: WebTest Cookbook
Marc Guillemot <firstname.lastname@example.org>
Mon, 11 Dec 2006 10:28:12 +0100
You're welcome! ;-)
A lot of things could/should be done to improve WebTest ... and are just
waiting that someone starts doing them. We are now 4 committers but 3 of
them don't have currently so much time/interest for WebTest. This
committers list isn't definitive at all and we would be happy to welcome
new energies. Even if you're not a programmer I'm sure that you could
contribute to WebTest for instance improving the documentation as you
If you want to start contributing I will help you as far as I can.
WebTest build process is good because it ensures a high quality but it
is surely too complex and not easy to start with.
PS: I don't agree with you on the reason motivating to use WebTest
rather than HtmlUnit to write tests. Even with a good HtmlUnit knowledge
I prefer to specify my tests with WebTest rather than to program them
with HtmlUnit: tests are shorter, more readable and more usable.
Nate Oster wrote:
> This thread about using Groovy to temporarily suppress JS exceptions is
> fantastic. However, I think it highlights the need for WebTest to be
> more "packaged" for new users. I know there are several open JIRA
> issues about this.
> For example, most of us "end users" of WebTest don't have detailed
> HTMLUnit knowledge - that's why we use WebTest! :)
> WebTest provides a simple, declarative, procedural layer of abstraction
> on top of HTMLUnit. Most WebTesters aren't familiar with all the
> available HTMLUnit settings. One way to help users take advantage of
> Groovy scripting would be to create a cookbook of common solutions like
> the one below - perhaps even including them as examples with the
> distribution (or optionally with the distribution). Maybe the wiki is
> the right place for this, but it seems to be little-used.
> As 2.3 or 3.0 or whatever the next version is takes shape, it would be
> really nice to poll this list for the design of an ideal WebTest
> distribution package that would help new users get productive
> Congrats on your presentation at iX Bessere Software Konferenz!
> Nate Oster
> Message: 4
> Date: Thu, 07 Dec 2006 17:26:18 +0100
> From: Marc Guillemot <email@example.com>
> To: firstname.lastname@example.org
> Subject: Re: [Webtest] Script exception with JS Enabled...
> Reply-To: email@example.com
> Reply-To: Marc Guillemot <firstname.lastname@example.org>
> as long as you don't have a fixed version, you can "locally ignore" the
> js errors with something like:
> <groovy description="don't react on js script errors">
> step.context.webClient.throwExceptionOnScriptError = false
> ... your page invocation here ...
> <groovy description="react on js errors again as this webtest should
> verify the quality of the application">
> step.context.webClient.throwExceptionOnScriptError = true