Ch1-Intro - Introduction to Software Testing Chapter 1...

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

View Full Document Right Arrow Icon
Introduction to Software Testing Chapter 1 Introduction Paul Ammann & Jeff Offutt www.introsoftwaretesting.com Introduction to Software Testing (Ch 1), www.introsoftwaretesting.com © Ammann & Of ut 2 A Talk in 3 Parts 1. Why do we test ? 2. What should we do during testing ? 3. How do we get to this future of testing ? We are in the middle of a We are in the middle of a revolution revolution in how software is tested in how software is tested Research is finally meeting practice Introduction to Software Testing (Ch 1), www.introsoftwaretesting.com © Ammann & Of ut 3 Here! Test This! MicroSteff – big software system for the mac V.1.5.1 Jan/2007 Verdatim DataLife MF2-HD 1.44 MB Big software program Jan/2007 My first “professional” job A stack of computer printouts—and no documentation Introduction to Software Testing (Ch 1), www.introsoftwaretesting.com © Ammann & Of ut 4 Cost of Testing In real-world usage, testing is the principle post-design activity Restricting early testing usually increases cost Extensive hardware-software integration requires more testing You ’re going to spend about half of re going to spend about half of your development budget on testing, whether you want to or not. whether you want to or not. Introduction to Software Testing (Ch 1), www.introsoftwaretesting.com © Ammann & Of ut 5 Part 1 : Why Test? Written test objectives and requirements are rare How much testing is enough? Common objective – spend the budget … If you don ’t know why you t know why you ’re conducting re conducting a test, it won ’t be very helpful. t be very helpful. Introduction to Software Testing (Ch 1), www.introsoftwaretesting.com © Ammann & Of ut 6 Why Test? “The software shall be easily maintainable” Threshold reliability requirements? Requirements definition teams should include testers! If you don ’t start planning for the test at the t start planning for the test at the time the functional requirements are formed, you ’ll never know why you ll never know why you ’re conducting the test. re conducting the test.
Background image of page 1

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

View Full DocumentRight Arrow Icon
Introduction to Software Testing (Ch 1), www.introsoftwaretesting.com © Ammann & Of ut 7 Cost of Not Testing Not testing is even more expensive Planning for testing after development is prohibitively expensive A test station for circuit boards costs half a million dollars … Software test tools cost less than $10,000 !!! Program Managers often say: “Testing is too expensive. Testing is too expensive. Introduction to Software Testing (Ch 1), www.introsoftwaretesting.com © Ammann & Of ut 8 Caveat: Impact of New Tools and Techniques They’re teaching a new way of plowing over at the Grange tonight - you going? Naw - I already don’t plow as good as I know how. ..
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.

This note was uploaded on 05/29/2010 for the course CS 514 taught by Professor Prof.j.bieman during the Fall '09 term at Colorado State.

Page1 / 9

Ch1-Intro - Introduction to Software Testing Chapter 1...

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