GeekArticles 
Testing CheckListsUsability Testing and Risk Management in a Multi-Developer Context
Author: stickyminds.com |
Published: 17th Aug 2005 |
Visited: 265 times |
Add CommentFiled in: CheckListsDriving usability improvement in a company with over 100 different remotely-located software development organizations, each using independent development processes, presents specific Software Quality challenges. This paper describes the usability acceptance testing and usability risk assessment approaches that one organization instituted within this complex development environment, from the ground up. The steps taken are outlined, along with charts presenting results data. The data show a 100% increase in customer satisfaction, a reduction in customer-reported usability problems, and order-of-magnitude improvements in testing cost reduction and turn-around time over a three-year period. Key success factors are highlighted.
Read Article Sponsored Links
Related Articles
• Swing Extreme Testing Book Review Swing Extreme Testing Book Review
Swing used to be a simple component offered as an add-on for Java. This plug-in can be used as a GUI (graphical user interface) to develop as an add-on for the Java application. It has the ability to emulate certain platforms eventually building a powerful applicat ...
• Swing Extreme Testing Swing Extreme Testing by Tim Lavers, Lindsay Peters
This book is a practical guide to automated software testing for extreme Java programming using Swing GUIs, with lots of ready-to-use real-life examples and source code for automated testing of the software components usually regarded as too hard ...
• Swing Extreme Testing - Outline of the Unit Test Outline of the Unit Test
The things we want to test are:
Initial settings:
The text field is empty.
The text field is a sensible size.
The Ok button is disabled.
The Cancel button is enabled.
The dialog is a sensible size.
...
• Swing Extreme Testing - Unit Test Infrastructure Unit Test Infrastructure
Having seen the broad outline of the test class and the UI methods needed, we can look closely at the implementation of the test. start with the UI Wrapper class and the init() and cleanup()method ...
• Swing Extreme Testing - The ShowerThread Class The ShowerThread Class
Since SaveAsDialog.show() blocks, we cannot call this from our main thread; instead we spawn a new thread. This thread could just be an anonymous inner class in the init()metho ...
• Swing Extreme Testing - The wasCancelled() Test The wasCancelled() Test
The first of our API tests is to check the wasCancelled() method. We will basically do three investigations. The first test will call wasCancelled()before the dialog has been cancelled. The second test will cancel the dialog and then call the method. In the third test we wil ...
• Swing Extreme Testing - The Data Validation Test The Data Validation Test
The Ok button of the SaveAsDialog should only be enabled if the name that has been entered is valid. A name can be invalid if it contains an illegal character, or if it has already been use ...
• Testing Multithreaded Java Code
In this interview from JavaOne 2008, Coverity chief scientist Andy Chou discusses why traditional unit tests often help in uncovering concurrency-related errors, and why a combination of static and dynamic analysis yields better results when testing multithreaded code.
...
