Re: [OVC-demo-team] New tester

From: Fred McLain <mclain_at_zipcon_dot_net>
Date: Wed Jan 28 2004 - 17:09:31 CST

Sure. What I am looking for is a list of steps that the user is expected
to perform and the responses the system is expected to give. In short,
requirements. Use cases are a simple way to describe these:

----
1. User hits any key
2. System says instructions on use
3. User hits down arrow
4. System says ballot title
5. User hits down arrow
6. System says first canidate name
7. User hits enter
8. System restates selection and asks for down arrow to confirm
9. User hits down arrow
10. System says "confirmed"
11. System says next ballot title
...
Exceptions:
at 9: User hits enter
10. System says canceling selection
11. go to step 4
----
One reference I found via a google search:
http://www.objectmentor.com/publications/usecases.pdf
Though I prefer the outline approach, you can also do this as a diagram:
http://www.agilemodeling.com/artifacts/useCaseDiagram.htm
No matter which approach we take, we need requirements in order to test, 
otherwise it's just opinion or saying "runs as coded".
	-Fred-
On Wed, 28 Jan 2004 14:02:15 -0800, Alan Dechert 
<alan@openvotingconsortium.org> wrote:
> Fred,
>
>>
>> Last time I talked to Al he was requesting more effort on the vision
>> impaired (audio) interface.  I have done some testing on it and found 
>> that
>> Jan's code didn't crash but I am confused about the work flow.
>>
>> Does anyone know if we have use cases for the audio interface?
>>
> Can you elaborate on this?
>
> Thanks.
>
> Alan (not Al, btw) D.
>
>
-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
==================================================================
= The content of this message, with the exception of any external 
= quotations under fair use, are released to the Public Domain    
==================================================================
Received on Thu Apr 1 02:40:12 2004

This archive was generated by hypermail 2.1.8 : Thu Apr 01 2004 - 02:40:36 CST