外文文献—软件测试.docxVIP

附录A外文翻译—原文部分 外文出处：Software Engineering Tenth Edition机械工业出版社2018版第八章202-212页。 Testing is intended to show that a program does what it is intended to do and to discover program defects before it is put into use. When you test software, you execute a program using artificial data. You check the results of the test run for errors, anomalies, or information about the program’s non-functional attributes. The testing process has two distinct goals: 1. To demonstrate to the developer and the customer that the software meets its requirements. For custom software, this means that there should be at least one test for every requirement in the requirements document. For generic software products, it means that there should be tests for all of the system features, plus combinations of these features, that will be incorporated in the product release. 2. To discover situations in which the behavior of the software is incorrect, undesirable, or does not conform to its specification. These are a consequence of software defects. Defect testing is concerned with rooting out undesirable system behavior such as system crashes, unwanted interactions with other systems, incorrect computations, and data corruption. The first goal leads to validation testing, where you expect the system to perform correctly using a given set of test cases that reflect the system’s expected use. The second goal leads to defect testing, where the test cases are designed to expose defects. The test cases in defect testing can be deliberately obscure and need not reflect how the system is normally used. Of course, there is no definite boundary between these two approaches to testing. During validation testing, you will find defects in the system; during defect testing, some of the tests will show that the program meets its requirements. The diagram shown in Figure 1 may help to explain the differences between validation testing and defect testing. Think of the system being tested as a black box. The system ac