Lecture Introduction to software engineering - Week 9: Software testing. In this chapter, you will learn to: Development testing, test-driven development, release testing, user testing. Invite you to find out the detailed content. | Week 9 Software Testing Nguyễn Thị Minh Tuyền Adapted from slides of Ian Sommerville https tailieudientucntt Software Testing 1. What is it 2. Who does it 3. What are the steps 4. What is the work product 5. How do I ensure that I ve done it right https tailieudientucntt Topics covered 1. Development testing 2. Test-driven development 3. Release testing 4. User testing 3 https tailieudientucntt Program testing Testing is intended p to show that a program does what it is intended to do and p 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. 4 https tailieudientucntt Program testing goals Validation testing To demonstrate to the developer and the customer that the software meets its requirements. Defect testing To discover situations in which the behavior of the software is incorrect undesirable or does not conform to its specification. 5 https tailieudientucntt An input-output model of program testing Input test data Inputs causing Ie anomalous behaviour System Outputs which reveal Output test results Oe the presence of defects 6 https tailieudientucntt Verification vs validation Verification quot Are we building the product right . p The software should conform to its specification. Validation quot Are we building the right product . p The software should do what the user really requires. 7 https tailieudientucntt V amp V confidence Aim of V amp V is to establish confidence that the system is fit for purpose .
