April15

April15 - Ian Sommerville 2000 Software Engineering, 6th...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 1 Defect testing Objectives To understand testing techniques that are geared to discover program faults To introduce guidelines for interface testing To understand specific approaches to object- oriented testing To understand the principles of CASE tool support for testing Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 2 The testing process Component testing Testing of individual program components Usually the responsibility of the component developer Tests are derived from the developers experience Integration testing Testing of groups of components integrated to create a system or sub-system The responsibility of an independent testing team Tests are based on a system specification Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 3 Defect testing The goal of defect testing is to discover defects in programs A successful defect test is a test which causes a program to behave in an anomalous way Tests show the presence, not the absence of defects Test data Inputs which have been devised to test the system Test cases Test data and the predicted outputs if the system operates according to its specification Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 4 Only exhaustive testing can show a program is free from defects However, exhaustive testing is impossible Testing old capabilities is more important than testing new capabilities Testing typical situations is more important than boundary value cases But boundary value cases should not be ignored! Testing priorities Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 5 Black-box testing An approach to testing where the program is considered as a black-box Nothing is known about the system structure The program test cases are based on the system specification Test planning can begin early in the software process Acceptance testing is an example of black-box testing Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 20 Slide 6 Black-box testing I e Input test data O e Output test results System Inputs causing anomalous behaviour Outputs which reveal the presence of defects Ian Sommerville 2000...
View Full Document

This note was uploaded on 06/16/2009 for the course CSCI 578 taught by Professor Nenadmedidovic during the Spring '08 term at USC.

Page1 / 22

April15 - Ian Sommerville 2000 Software Engineering, 6th...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online