Successfully reported this slideshow.
Your SlideShare is downloading. ×

What your boss needs to know about sw testing

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 4 Ad

What your boss needs to know about sw testing

Download to read offline

One of the most frequent comments I hear from participants in my courses is "My boss should attend this course". Since we are talking about "bosses" I decided to make some of my course content available as a comic book.

One of the most frequent comments I hear from participants in my courses is "My boss should attend this course". Since we are talking about "bosses" I decided to make some of my course content available as a comic book.

Advertisement
Advertisement

More Related Content

More from Phil Robinson (17)

Recently uploaded (20)

Advertisement

What your boss needs to know about sw testing

  1. 1. What Your Boss Needs to Know About Software Testing Phil Robinson Hope its not coming out of my budget We’ve organised a software testing course Software Testing Techniques for Improving Software Quality Great! LonsdaleSystems.com P hil Robins on phil@lonsdalesystems.com www.lonsdalesystems.com © Lonsdale Systems Our boss should attend this course! 1 Now lets apply what you learnt! We need to QA the software and remove all the bugs. According to the CMMI “the purpose of quality assurance is to provide staff and management with objective insight into processes and associated work products” Actually our instructor pointed out that you use the term “QA” incorrectly! We also learnt that testers don’t remove bugs from software. Developers do! Testing is only one aspect of QA! Cause of Software Failures Developers make the errors that result in defects… People  Error (mistake) © L ons dale S ys tems Defect (fault, bug) Failure …testers identify failures caused by defects… 2 …leaving the developers to find and remove the defects www.lonsdalesystems.com
  2. 2. I wonder if testing is still on schedule? Test Activities Testing “Testing” is not a single activity that is scheduled after development! Our instructor also pointed out how unrealistic your project plans are! © Lons dale S ys tems 9 Test planning and control Test analysis and design So instead of complaining that the project was “held up” in testing… Test Activities Test implementation and execution Defect repair Evaluating exit criteria and reporting Test closure activities © Lons dale S ys tems 10 …it would in fact be more accurate to say it was “held up in repair”! I wonder if they found all the bugs yet? Software Testing Testing All Paths • Possible paths = 520+519+518+…51 = 1017 • 5 minutes per test case – 1 billion years • 5 microseconds per test case – 19 years loop <= 20 © Lons dale S ys tems Actually its impossible to find “all the bugs”! www.lonsdalesystems.com 4
  3. 3. Principle 1: Testing Shows Presence of Defects Software Testing Testing All Inputs       • Possible combinations = 28 = 256 © L ons dale S ys tems 5 © L ons dale S ys tems 10 OK! But since we have found lots of bugs we’re must be making good progress. Yes? Principle 2: Exhaustive Testing Is Impossible    © L ons dale S ys tems       11 Actually, finding a bug increases the likelihood of finding more bugs! So the harder we work, the more work we have to do? That makes no sense at all! Principle 4: Defect Clustering       © Lons dale S ys tems             13 That must be why testing is so expensive? www.lonsdalesystems.com
  4. 4. Cost of Quality Cost of Quality Cost Actually testing seems expensive because you focus on the cost of testing rather than the cost of quality. Cost of im quality proving Cost of po or quality Quality © L ons dale S ys tems 13 Rising Cost of Rework Principle 3: Early Testing $200       $50 $20 $5 $1 Requirements Design Construction Operation Deployment © L ons dale S ystems 22 © L ons dale S ystems How did the course go? Lots of trendy nonsense! Actually many of these ideas have been around since the 1970s! www.lonsdalesystems.com 12

×