Chapter 8 – Software Testing. This lecture discuss the key concepts related to software process improvement. Triple constraint is the most important concern for project managers and software process infrastructure plays important role in successful project completion. The assessment of existing process based on the defined effective process may help in successful project completion. | Chapter 8 – Software Testing Chapter 8 Software Testing 1 30/10/2014 Topics covered Development testing Test-driven development Release testing User testing Chapter 8 Software Testing 2 30/10/2014 Program testing 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. Can reveal the presence of errors NOT their absence. Testing is part of a more general verification and validation process, which also includes static validation techniques. Chapter 8 Software Testing 3 30/10/2014 Program testing goals 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. To discover situations in which the behavior of the software is incorrect, undesirable or does not conform to its specification. Defect testing is concerned with rooting out undesirable system behavior such as system crashes, unwanted interactions with other systems, incorrect computations and data corruption. Chapter 8 Software Testing 4 30/10/2014 Validation and defect testing The first goal leads to validation testing 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 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. Chapter 8 Software Testing 5 30/10/2014 Testing process goals Validation testing To | Chapter 8 – Software Testing Chapter 8 Software Testing 1 30/10/2014 Topics covered Development testing Test-driven development Release testing User testing Chapter 8 Software Testing 2 30/10/2014 Program testing 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. Can reveal the presence of errors NOT their absence. Testing is part of a more general verification and validation process, which also includes static validation techniques. Chapter 8 Software Testing 3 30/10/2014 Program testing goals 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
