万古神帝笔下文学:谁能帮忙翻译下这篇计算机文章?

7 Program testing/debugging
7.1 Introduction
Although many authors attempt to draw a distinction between testing and debugging a program, in practical terms they amount to the same thing. Consequently, the term testing is used to cover this procedure.
Testing is the process of executing a program with the deliberate intent of finding errors. This definition is important because it specifies a state of mind on the part of the person performing the test. It is akin to the engineering practice of testing a mechanism or structure not only to verify that it can perform its designed task under ideal conditions but also to determine the point (if any) at which it fails.

7.2 Testing in its correct perspective
Diligent and exhaustive testing is no substitute for careful design. The time taken to test a program to satisfaction will be in proportion (with an inverse ratio) to the time taken in designing the program before its coding. Days spent in design will save weeks in testing.
The elegance of design of any program will directly affect both the ease of testing the program and the incidence of errors detected. Errors will not be referred to as ‘bugs’ because gracing them with a euphemism makes it easier for us as programmers to ignore the fact that they are errors. They are faults in the execution of a program which have been induced by the programmer through poor design or incorrect logic.
Most errors are the result of incorrect control functions in programs rather than incorrect computation or data manipulation. The latter types of error are usually the easiest to detect and correct; the former often go undetected and remain in programs after they have been approved to run in a production (or ‘live’) environment. Control functions are those which regulate the sequence in which tasks are performed, the selection of appropriate processing modules for a given situation, the number of times a loop is executed, and so on.