Hey, I've got an idea: why have humans even review
the test results? I mean, that's just a suggestion that the script can't
fix whatever problem is in the code that's under test, right? In fact, why
have humans write the test scripts at all? That really smells like we need
humans involved in the testing process, doesn't it? Aren't you, like, some
total loser if you cant get automation to write the test scripts on its
own?
- Maybe Michael wants to pause and review a
screen with his own eyes before the next step.
- Maybe Michael wants to be notified when a bug is found,
as one might do with a broken build and a lava lamp.
- Maybe Michael wants to vary some aspect of the test at
some specific point, based on the result of a previous test.
- Maybe Michael wants to be notified immediately upon each
step of a test being completed.
- Maybe this isn't a test that runs with the build
process.
I applaud the use of whatever aspects of human cognition
want to use in concert with automation.
---Michael B.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charley Baker
Sent: June 5, 2006 7:00 PM
To: [email protected]
Subject: Re: [Wtr-general] Beep for intervention?
-Charley
On 6/5/06, Michael
Moore <[EMAIL PROTECTED]>
wrote:
> > I've got a script that can take some time to run, and needs human
> > intervention in a couple parts. Is there a way to have Watir beep or
> > make some sort of audio notification?
>
> print "\a"
>
> Don't tell anybody I told you. :)
I won't mention it.
Thanks,
--
Michael Moore
-------------------------------
www.stuporglue.org -- Donate your used computer to a student that needs it.
www.ubuntu-utah.org -- In Utah? Interested in Ubuntu? Come join us.
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
