|
Usability Testing Event Diagnosis Checklist (template) When usability tests detect "non-correct" user behaviors, you still need a way to pinpoint the source of the problem. Is it a problem with the test itself, with the tasks you're asking your users to perform, or something else altogether? In hundreds of usability tests, the checklist offered here has been shown to be a useful tool for answering those questions--allowing the tester to categorize the type of problem that a test subject is having.
|
|
|
Giving the Human Touch to Software Yogita works as a QA/testing professional with Mindfire Solutions, and has written a number of articles on QA and testing strategies. Yogita is currently exploring thoughts of beauty as an area of testing and its relation to usability. Her role at Mindfire has been to implement Quality processes throughout the organization and build a dedicated testing team. The team recently published a White Paper “Porting projects: Test techniques,” downloadable from www.mindfiresolutions.com. Yogita can be reached at [email protected].
|
|
|
Avoiding the Script Cemetery It's frightening how many companies are on their second, third, or even greater attempt to automate their testing—each time junking months or years of effort and work product. Here, test automation advisor Linda Hayes shows the way to avoid having to bury your automation project.
|
|
|
Internet Accessibility Ever try to navigate the Web with your eyes closed? Without a mouse? Fifty million Americans are differently-abled, and nearly half of these people encounter difficulties accessing the World Wide Web. The U.S. government recently took steps to tackle the accessibility issue. Here's some coverage of the issue.
|
|
|
The Wonderful World of Software Former STQE magazine Technical Editor Brian Lawrence shares a tale about why a commitment to quality and paying close attention to detail are critical elements in building better software. It's all about careful planning and anticipating customer behavior. Go with Brian on a stroll through one of the oldest, best-known amusement parks to find out more.
|
|
|
Making Sure You Buy the Right Packaged-Software Solution The slick brochure promises every feature you can imagine, and the sales rep assures you that his package will do just what your users want. But that's what the other vendor's sales rep said, too. Sound familiar? Karl Wiegers recommends several requirements development practices that can help you select the right commercial package solution. Key practices include identifying user classes, defining their use cases, creating test cases from the high-priority use cases, documenting pertinent business rules, and exploring the users' performance goals and other quality attributes.
|
|