[Webtest] WebTest and CruiseControl
Thu, 08 Apr 2004 08:48:06 -0400
Could you speed up test execution by using <parrallel> in Ant to
launch separate test suites at the same time? This assumes you have
the hardware resources to do so, but usally you're running
CruiseControl on a reasonably fast machine.
For results reporting, you might consider adding an Ant task that
automatically applies the XSL transformation to the XML results. You
could modify the template to place failures in a summary table for
quicker investigation. Since you've probably got a webserver on your
CruiseControl box, dropping the results HTML pages into a browsable
directory would further speed things up. It's not an ideal solution,
but it might make your life easier with a minimum of hacking.
----- Original Message -----
Date: Wednesday, April 7, 2004 8:12 pm
Subject: [Webtest] WebTest and CruiseControl
> Hello everyone,
> We're running our WebTests with after every check in using
> CruiseControl. It works well except that sometimes when there's a
> failure, it's hard to know what went wrong. CruiseControl sends
> an email with the error output from WebTest, but that doesn't
> always help, and we have to look at the actual html result files
> to see the real error. For example, today the build server ran
> out of memory, CruiseControl (and WebTest) just reported a server
> error 500, and I had to look at the last html result page to see
> the out of memory error.
> Also, I'm wondering if we should really run these tests after
> every build, or would it be best to do it only on the nightly
> build, since they aren't that fast. The programmers like the
> safety net of running them every build, particularly as we don't
> have many unit tests yet.
> Does anyone using CruiseControl have any helpful hints for us?
> WebTest mailing list