[Wtr-general] Automating the running & reporting of watir tests

Charley Baker charley.baker at gmail.com
Tue Dec 19 16:46:14 EST 2006


Yes, no, maybe. :) Simple answer. I'm using Watir tests, and running them
through Cruise Control, so that they're continuous integration tests,
reports generated through http://test-report.rubyforge.org/. xml reports,
cruise picks them up since they're xunit style and publishes them out.
Cruise emails the reports out.

Where to locate it in svn is a good question. We currently have our FAT in
it's own location. We also have a ruby install in svn, for better or worse,
which is able to be run in ci and on any workstation, and able to easily
update for shared libraries.

-Charley

On 12/19/06, Thomas.Vaughan at usitc.gov <Thomas.Vaughan at usitc.gov> wrote:
>
> Hi,
>
> I just started using WATIR and fell in love at first sight.  I'm sure
> what I'm trying to do has been done before, so I thought I'd throw a net
> out here and see what I catch...
>
> Our dev team is building a half-dozen different apps (WARs) that, as a
> whole, will eventually replace a legacy application.  We've started
> writing WATIR tests to check some of the individual WARs, but what I'm
> hoping to do is get some advise on:
>
>         1) How do people schedule automatic execution of a bunch of
> different WATIR tests, similar to Continuum might do.  Is everyone out
> there writing their own cron + scripts?
>
>         2) Is there are pre-built "watir-harness" that will email
> someone when a test doesn't run as expected?
>
>         3) Do people typically source control their WATIR tests along
> side the code that's under test?  Or do they typically group all their
> WATIR tests together in a separate project for
> ease-of-reuse/ease-of-discovery purposes?
>
> Thanks in advance!
> Tom Vaughan
>
> _______________________________________________
> Wtr-general mailing list
> Wtr-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/wtr-general/attachments/20061219/a4b9eefe/attachment.html 


More information about the Wtr-general mailing list