i've got 99 problems and code defects are

33
I've got 99 problems and code defects are one

Upload: dag-rowe

Post on 07-Jul-2015

323 views

Category:

Software


2 download

DESCRIPTION

The presentation with the talk is available at https://www.youtube.com/watch?v=z9K8CCE5aBY This is internal talk for a general non-tester audience. It borrows heavily from the following sources: Software Entomology or Where Do Bugs Come From? - Noah Sussman - http://www.slideshare.net/noahsussman/software-entomology-or-where-do-bugs-come-from http://infiniteundo.com/ - Various posts by Noah Sussman Lessons Learned in Software Testing - Cem Kaner, James Bach, Bret Pettichord Foundations of Software Testing - http://www.testingeducation.org/BBST/foundations Epic failures: 11 infamous software bugs - http://www.computerworld.com/s/article/9183580/Epic_failures_11_infamous_software_bugs How to Change Software Testing for New Cloud Configurations - http://www.cio.com/article/2386122/developer/how-to-change-software-testing-for-new-cloud-configurations.html

TRANSCRIPT

Page 1: I've got 99 problems and code defects are

I've got 99 problems and code

defects are one

Page 2: I've got 99 problems and code defects are
Page 3: I've got 99 problems and code defects are

Testing seeks to

discover threats to the

value of software

Page 4: I've got 99 problems and code defects are

Debugging discovered 1949

I can remember the exact

instant when I realized that a

large part of my life … was

going to be spent finding

mistakes in my own programs

- Maurice Wilkes

Page 5: I've got 99 problems and code defects are

Epic failure

• Mars Climate Orbiter doesn't orbit

– $327 million project lost in a minute

• Didn’t approach at correct angle to planet

• Actual thrust was 4.45 times larger than desired

• Therac-25 Medical Accelerator disaster

– Several deaths documented

– Software race condition decided your treatment

• Low power electron beam

• Megavolts of X-Rays

Page 6: I've got 99 problems and code defects are

One in a million is next Tuesday

• You have a bug

• You say

– Maybe this is what is happening!

– But the chance of it happening is one in a million!

• At computer speeds you can hit the millionth

execution ‘Next Tuesday’

Page 7: I've got 99 problems and code defects are

Welcome to QA

Page 8: I've got 99 problems and code defects are
Page 9: I've got 99 problems and code defects are

The test role

• Questioning a product in order to evaluate it

– James Bach

• Testing is done to find information

– With that information critical project decisions can be

made

Page 10: I've got 99 problems and code defects are

Project headlights

• Imagine the team packed into a 4 x 4 driving off

road at night

• You’re going to want some headlights

• Testers illuminate where you are and the

obstacles they see

• Other team members can decide if we keep

going or turn back

Page 11: I've got 99 problems and code defects are
Page 12: I've got 99 problems and code defects are

A test mission

• Find important problems fast

• Perform a comprehensive quality assessment

• Maximize testing efficiency

• Assure the test process is accountable

Page 13: I've got 99 problems and code defects are
Page 14: I've got 99 problems and code defects are

I'm not schooled in the

science of human factors, but

I suspect surprise is not an

element of a robust user

interface

- Chip Rosenthal

Page 15: I've got 99 problems and code defects are
Page 16: I've got 99 problems and code defects are

Debugging is twice as hard

as writing the code in the first

place

- Brian Kernighan

Page 17: I've got 99 problems and code defects are
Page 18: I've got 99 problems and code defects are

You’re scaring me. So now what?

Test activities• You find information when you

– Observe

– Record

– Reproduce

– Infer

– Inform

– Collaborate

Page 19: I've got 99 problems and code defects are
Page 20: I've got 99 problems and code defects are

QA Guiding Value

Observation beats

speculation every time

Page 21: I've got 99 problems and code defects are

How do I science?

Writing a bug report

1. Description

– What you expected to happen

– What actually happened

2. Steps to Reproduce

Page 22: I've got 99 problems and code defects are
Page 23: I've got 99 problems and code defects are

An app’s hierarchy of needs

Page 24: I've got 99 problems and code defects are

I've got 99 problems

and code defects are

one

Page 25: I've got 99 problems and code defects are
Page 26: I've got 99 problems and code defects are

Enough testing

“It works”

• Means that it appears to meet the requirements

to some degree

“Enough testing”

• Means the team has enough information to

make good decisions

Page 27: I've got 99 problems and code defects are

So what’s in it for me?

Page 28: I've got 99 problems and code defects are

Find the threats to the value of your

work• Be empirical

– Find evidence based on observation

– Make some valid inferences

– Justify your beliefs about the project

– Clarify and banish ambiguity in project

language and results

Page 29: I've got 99 problems and code defects are
Page 30: I've got 99 problems and code defects are
Page 31: I've got 99 problems and code defects are
Page 32: I've got 99 problems and code defects are
Page 33: I've got 99 problems and code defects are

Sources

• Software Entomology or Where Do Bugs Come From?

– Noah Sussman

– http://www.slideshare.net/noahsussman/software-entomology-or-where-do-bugs-come-from

• http://infiniteundo.com/

– Various posts by Noah Sussman

• Lessons Learned in Software Testing

– Cem Kaner, James Bach, Bret Pettichord

• Foundations of Software Testing

– http://www.testingeducation.org/BBST/foundations

• Epic failures: 11 infamous software bugs

– http://www.computerworld.com/s/article/9183580/Epic_failures_11_infamous_software_bugs

• How to Change Software Testing for New Cloud Configurations

– http://www.cio.com/article/2386122/developer/how-to-change-software-testing-for-new-cloud-configurations.html