Ch1-Introduction

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

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

View Full Document Right Arrow Icon
1 Introduction to Software Testing Chapter 1 Introduction & The Model-Driven Test Design Process Paul Ammann & Jeff Offutt http://www.cs.gmu.edu/~offutt/softwaretest/ Updated 24-August 2010 Testing in the 21st Century Software defines behavior – network routers, finance, switching networks, other infrastructure Today’s software market : Industry is going – is much bigger – is more competitive – has more users Embedded Control Applications – airplanes, air traffic control – spaceships watche – PDAs – memory seats – DVD players through a revolution in what testing means to the success of software products – watches – ovens – remote controllers Agile processes put increased pressure on testers – Programmers must unit test – with no training, education or tools ! – Tests are key to functional requirements – but who builds those tests ? Introduction to Software Testing (Ch 1) © Ammann & Offutt 2 – garage door openers – cell phones
Background image of page 1

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

View Full DocumentRight Arrow Icon
2 OUTLINE 1. Spectacular Software Failures 2. Why Test? 3. What Do We Do When We Test ? Test Activities and Model-Driven Testing 4. Software Testing Terminology Introduction to Software Testing (Ch 1) © Ammann & Offutt 3 5. Changing Notions of Testing 6. Test Maturity Levels 7. Summary The First Bugs Hopper’s “bug” (moth stuck in a relay on an early machine “It has been just so in all of my inventions. The first step is an intuition, and comes with a burst, then difficulties arise—this thing “an analyzing process must equally have been performed in order to furnish the Analytical Engine with the necessary operative data; and that herein early machine) Introduction to Software Testing (Ch 1) © Ammann & Offutt 4 gives out and [it is] then that 'Bugs'—as such little faults and difficulties are called—show themselves and months of intense watching, study and labor are requisite. . .” – Thomas Edison may also lie a possible source of error. Granted that the actual mechanism is unerring in its processes, the cards may give it wrong orders. ” – Ada, Countess Lovelace (notes on Babbage’s Analytical Engine)
Background image of page 2
3 Costly Software Failures NIST report, “The Economic Impacts of Inadequate Infrastructure for Software Testing” (2002) – Inadequate software testing costs the US alone between $22 and $59 billion annually – Better approaches could cut this amount in half Huge losses due to web application failures – Financial services : $6.5 million per hour (just in USA!) – Credit card sales applications : $2.4 million per hour (in USA) In Dec 2006, amazon.com’s BOGO offer turned into a Introduction to Software Testing (Ch 1) © Ammann & Offutt 5 double discount 2007 : Symantec says that most security vulnerabilities are due to faulty software World World-wide monetary loss due wide monetary loss due to poor software is staggering Spectacular Software Failures Mars Polar Lander crash site?
Background image of page 3

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

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

Page1 / 46

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

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

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