[Webtest] WebTest and CruiseControl
Thu, 08 Apr 2004 21:55:42 +0000
We now have the Canoo test results included in the build results email sent by Cruise Control, and can access the HTML results pages (including the summaries) through the Build Artifacts on the CruiseControl result web page. So if anyone wants to know how to do this, just ask. It is way cool! (Now we just need more tests!)
> Regarding XSL transformation of results:
> The only way I've done the XSL transformation is by simply
> right-clicking the XML result summary in NetBeans and applying the
> sample reportfromSummary.xsl stylesheet that came with the distribution.
> The results are well-organized and human-readable. Clearly, I need to
> connect this approach to Ant in order to have it scale.
> I promise to share whatever we generate.
> Speaking of sharing, I posted a question to the forum regarding XSL
> transformation of XML TEST CASES, but haven't received any responses.
> Hasn't anyone generated HTML documentation for the XML test cases using
> this technique? Care to share an example stylesheet?
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of firstname.lastname@example.org
> Sent: Thursday, April 08, 2004 10:55 AM
> To: email@example.com
> Subject: Re: [Webtest] WebTest and CruiseControl
> Hi Nate,
> These are great ideas, we'll try them. Right now our build machine is
> very short of memory, but we will soon install a fast new one so we can
> try the parallel idea.
> I have been trying to find out how to apply XSL transformation to the
> XML results. Do you have any examples of how to do that? thanks, Lisa
> > Lisa,
> > 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.
> > Thanks,
> > Nate
> > ----- Original Message -----
> > From: firstname.lastname@example.org
> > 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?
> > >
> > > thanks,
> > > Lisa
> > > _______________________________________________
> > > WebTest mailing list
> > > WebTest@lists.canoo.com
> > > http://lists.canoo.com/mailman/listinfo/webtest
> > >
> > _______________________________________________
> > WebTest mailing list
> > WebTest@lists.canoo.com
> > http://lists.canoo.com/mailman/listinfo/webtest
> WebTest mailing list
> WebTest@lists.canoo.com http://lists.canoo.com/mailman/listinfo/webtest
> WebTest mailing list