I agree with Pauric. This was our biggest sore point at my last company, too. Manual testing was the only way we could catch all but the most fundamental design flaws. One thing that helped with the manual testing was having the tester involved with the design process. We occasionally ran an extra usability study session against the initial design prototype with the operations, support and test team members (sometimes the same person =]) just to make sure they knew what to look for. Obviously, that adds even more time, so we couldn't always do it.
Perhaps the evolution of prototyping applications that document in more detail will eventually yield automatic tests against design & behaviors. Might happen right around the same time robots take over the world =] Bryan http://www.bryanminihan.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of pauric Sent: Tuesday, December 04, 2007 9:19 AM To: [EMAIL PROTECTED] Subject: Re: [IxDA Discuss] how to test GUI requirements Sorry I cant be of help, but I share your pain, wanted to let you know we drew a blank and rely on expensive manual testing. ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
