ch23 - Software testing Ian Sommerville 2004 Software...

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

View Full Document Right Arrow Icon
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 23 Slide 1 Software testing
Background image of page 1

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

View Full DocumentRight Arrow Icon
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 23 Slide 2 Objectives To discuss the distinctions between validation testing and defect testing To describe the principles of system and component testing To describe strategies for generating system test cases To understand the essential characteristics of tool used for test automation
Background image of page 2
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 23 Slide 3 Topics covered System testing Component testing Test case design Test automation
Background image of page 3

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

View Full DocumentRight Arrow Icon
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 23 Slide 4 The testing process Component testing Testing of individual program components; Usually the responsibility of the component developer (except sometimes for critical systems); Tests are derived from the developer’s experience. System 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.
Background image of page 4
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 23 Slide 5 Testing phases
Background image of page 5

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

View Full DocumentRight Arrow Icon
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 23 Slide 6 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
Background image of page 6
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 23 Slide 7 Testing process goals Validation testing To demonstrate to the developer and the system customer that the software meets its requirements; A successful test shows that the system operates as intended. Defect testing To discover faults or defects in the software where its behaviour is incorrect or not in conformance with its specification; A successful test is a test that makes the system perform incorrectly and so exposes a defect in the system.
Background image of page 7

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

View Full DocumentRight Arrow Icon
©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 23 Slide 8 The software testing process
Background image of page 8
Software Engineering, 7th edition. Chapter 23 Slide 9 Only exhaustive testing can show a program is free from defects. However, exhaustive testing is impossible, Testing policies define the approach to be used in selecting system tests: All functions accessed through menus should be tested; Combinations of functions accessed through the same menu should be tested; Where user input is required, all functions must be tested with correct and incorrect input. Testing policies
Background image of page 9

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

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

This note was uploaded on 10/01/2010 for the course CS 1292 taught by Professor Aabdollah during the Spring '10 term at NJ City.

Page1 / 55

ch23 - Software testing Ian Sommerville 2004 Software...

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

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