This article makes three points. First, errors happen. Second, systems can encourage errors. Third, a basic understanding of the kinds of errors humans make can help us design better systems. Here are some suggestions to help avert trouble.
 

If you're paying the bill for all the graphics, glitz, and applets, you're going to want to have some evidence that thousands of potential customers have actually seen your Web site. Here is a step-by-step recipe for testing system, network, and Internet reporting systems.

A use case is a sequence of actions performed by a system, which combined together produce a result of value to a system user. Use cases describe the "process flows" through a system based on its actual likely use, so the test cases derived from use cases are most useful in uncovering defects in the process flows during real-world use of the system. Here is an example of how a use case is used to derive and prioritize test cases.

Tracking test results is one of the fundamental tasks that your software testing organization must perform to be successful. Explore how a customized database can enhance that process.