Shows how and why errors get introduced into examples in computer software documentation and what actions technical communicators can take to minimize this occurrence. Proposes a method to test examples. Suggests that technical writers can avoid these sources of error by creating and implementing a good test plan, maintaining and updating the plan, and benchmarking to improve examples. (RS)