lecture-16-when-to-stop-6

lecture-16-when-to-stop-6 - Lecture 16 - When to stop...

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

View Full Document Right Arrow Icon
Lecture 16 - When to stop testing? Spring 2010 CSci 5802 - Dr. Mats Heimdahl 1 Spring 2010 CSci 5802 - Dr. Mats Heimdahl 1 When to Stop Testing When have we tested enough? Today’s Topics How do we know when we are done? Stopping Criteria • Coverage • Budget Spring 2010 CSci 5802 - Dr. Mats Heimdahl 2 •P l an • Reliability • Mutation analysis When do we stop? The all important question When have we tested enough? Spring 2010 CSci 5802 - Dr. Mats Heimdahl 3 When We Have Achieved Coverage Set your sights on some coverage criteria and test until that is achieved. Problems? Spring 2010 CSci 5802 - Dr. Mats Heimdahl 4 The Budget Coverage Criterion Industry’s answer to “when is testing done” • When the money is used up • When the deadline is reached Spring 2010 CSci 5802 - Dr. Mats Heimdahl 5 Problems? Plan to Test—Test to the Plan Plan your tests carefully; then test according to plan When the tests are done—you are done. Spring 2010 CSci 5802 - Dr. Mats Heimdahl 6
Background image of page 1

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

View Full DocumentRight Arrow Icon
Lecture 16 - When to stop testing? Spring 2010 CSci 5802 - Dr. Mats Heimdahl 2 Spring 2010 CSci 5802 - Dr. Mats Heimdahl 7 Software Reliability Categorizing and specifying the reliability of software systems What Is Reliability? Probability of failure-free operation for a specified time in a specified environment for a given purpose This means quite different things depending Spring 2010 CSci 5802 - Dr. Mats Heimdahl 8 on the system and the users of that system Informally, reliability is a measure of how well system users think it provides the services they require Input test data Ie Input causing anomalous behavior Black-Box Testing Spring 2010 CSci 5802 - Dr. Mats Heimdahl 9 Output results Software Oe Output which reveal the presence of defects Reliability Improvement Reliability is improved when software faults which occur in the most frequently used parts of the software are removed Removing x% of software faults will not Spring 2010 CSci 5802 - Dr. Mats Heimdahl 10 necessarily lead to an x% reliability improvement • In a study, removing 60% of software defects actually led to a 3% reliability improvement Removing faults with serious consequences is the most important objective Input causing failure Reliability Perception User 1 Spring 2010 CSci 5802 - Dr. Mats Heimdahl 11 User 3
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 5

lecture-16-when-to-stop-6 - Lecture 16 - When to stop...

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

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