Skip to main content
padlock icon - secure page this page is secure

Testing Examples: A Guide

Buy Article:

$15.00 + tax (Refund Policy)

Errors occur in computer documentation for several reasons, especially when the writer depends on inspections to detect errors, assumes that an example works on all operating systems,enhances code with a word processor,gets stable code after documentation is complete,tests one time only,must use complex examples,does quick-and-dirty testing at the command line, or does incomplete testing. Writers can avoid these sources of errors by creating and implementing a good test plan, maintaining and updating the plan, and benchmarking to improve examples.
No References
No Citations
No Supplementary Data
No Article Media
No Metrics

Document Type: Journal Article

Publication date: February 1, 1995

More about this publication?
  • Technical Communication, the Society's journal, publishes articles about the practical application of technical communication theory and serves as a common arena for discussion by practitioners. Technical Communication includes both quantitative and qualitative research while showcasing the work of some of the field's most noteworthy writers. Among its most popular features are the helpful book reviews. Technical Communication is published quarterly and is free with membership.
  • Information for Authors
  • Subscribe to this Title
  • Membership Information
  • Ingenta Connect is not responsible for the content or availability of external websites
  • Access Key
  • Free content
  • Partial Free content
  • New content
  • Open access content
  • Partial Open access content
  • Subscribed content
  • Partial Subscribed content
  • Free trial content
Cookie Policy
Cookie Policy
Ingenta Connect website makes use of cookies so as to keep track of data that you have filled in. I am Happy with this Find out more