Lecture Introduction to software engineering - Week 9: Software testing

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.
Nội dung trích xuất từ tài liệu:
Lecture Introduction to software engineering - Week 9: Software testing Week 9: Software Testing Nguyễn Thị Minh Tuyền Adapted from slides of Ian Sommerville CuuDuongThanCong.com https://fb.com/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? CuuDuongThanCong.com https://fb.com/tailieudientucntt Topics covered 1. Development testing 2. Test-driven development 3. Release testing 4. User testing 3 CuuDuongThanCong.com https://fb.com/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 CuuDuongThanCong.com https://fb.com/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 CuuDuongThanCong.com https://fb.com/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 CuuDuongThanCong.com https://fb.com/tailieudientucntt Verification vs validation £ Verification: 'Are we building the product right”. p The software should conform to its specification. £ Validation: 'Are we building the right product”. p The software should do what the user really requires. 7 CuuDuongThanCong.com https://fb.com/tailieudientucntt V & V confidence £ Aim of V & V is to establish confidence that the system is 'fit for purpose'. £ Depends on p Software purpose: The level of confidence depends on how critical the software is to an organisation. p User expectations: Users may have low expectations of certain kinds of software. p Marketing environment: Getting a product to market early may be more important than finding defects in the program. 8 CuuDuongThanCong.com https://fb.com/tailieudientucntt Inspections and testing £ Software inspections p Concerned with analysis of the static system representation to discover problems(static verification) p May be supplement by tool-based document and code analysis. £ Software testing p Concerned with exercising and observing product behaviour (dynamic verification) p The system is executed with test data and its operational behaviour is observed. 9 CuuDuongThanCong.com https://fb.com/tailieudientucntt Inspections and testing Inspections Requirements Software UML design Database Program specification architecture models schemas System prototype Testing 10 CuuDuongThanCong.com https://fb.com/tailieudientucntt Software inspections £ Involve people examining the source representation with the aim of discovering anomalies and defects. £ Do not require execution of a system so may be used before implementation. £ May be applied to any representation of the system (requirements, design, configuration data, test data, etc.). £ Have been shown to be an effective technique for discovering program errors. 11 CuuDuongThanCong.com h ...