From: Fourchette Fourchette <alexisdal@...>
Date: 2010-08-19T21:46:42+09:00
Subject: when test just can't be automated

hi there,

i do hope i'm posting at the right place.

I am supposed to test some sort of a network device let's say. i want to
do it with ruby unit testing framework.

Basically you can send it commands using TCP/IP in a custom language
made for the device. It also sends back results.

so basically pretty much a lot of commands can be tested.

But some can not be completly automated.

for instance, this little devices beeps. There is a command to disable
sound. You can check that the command reported something like "sound
successfully disabled"

but the ruby script can't actually "hear" that the device has stopped
emitting sound after the command has been issued.

So i was thinking of having the test script do something like

init device
send a command that should make the device beep
--> at this point have the script stop and ask tester for confirmation
that a sound has been heard (ex: by hitting SPACE the test confirms that
she heard the sound)
send a command to disable sound
send a command that should normally have the device beeping
--> again ask the test to confirm no sound was heard

what's the best way to implement this ? do you have a suggestion ? (the
testers using the scripts aren't techies... :())

thanks
fourchette
-- 
Posted via http://www.ruby-forum.com/.