Purpose of Testing Beizer s testing levels on test process - - PowerPoint PPT Presentation

purpose of testing
SMART_READER_LITE
LIVE PREVIEW

Purpose of Testing Beizer s testing levels on test process - - PowerPoint PPT Presentation

Purpose of Testing Beizer s testing levels on test process maturity There are four levels of maturity Fundamental differences In viewpoint Effect on the individual Effect on the organization


slide-1
SLIDE 1

Purpose of Testing

slide-2
SLIDE 2

POT–2

Beizer’s testing levels on test process maturity

 There are four levels of maturity

 Fundamental differences

 In viewpoint  Effect on the individual  Effect on the organization  Effect on developed systems

slide-3
SLIDE 3

POT–3

Beizer’s testing levels on test process maturity

 Level 0

 No difference between testing and debugging

slide-4
SLIDE 4

POT–4

Level 0

 No difference between testing and debugging

 Adopted by undergraduate CS students

slide-5
SLIDE 5

POT–5

Level 0

 No difference between testing and debugging

 Adopted by undergraduate CS students

 Get their programs to compile

slide-6
SLIDE 6

POT–6

Level 0

 No difference between testing and debugging

 Adopted by undergraduate CS students

 Get their programs to compile  Debug with few arbitrarily chosen inputs or those

provided by the instructor

slide-7
SLIDE 7

POT–7

Level 0

 No difference between testing and debugging

 Adopted by undergraduate CS students

 Get their programs to compile  Debug with few arbitrarily chosen inputs or those provided by

the instructor

 Does not distinguish between incorrect program behaviour

and programming mistakes

slide-8
SLIDE 8

POT–8

Level 0

 No difference between testing and debugging

 Adopted by undergraduate CS students

 Get their programs to compile  Debug with few arbitrarily chosen inputs or those provided by

the instructor

 Does not distinguish between incorrect program behaviour and

programming mistakes

 Does little to help develop programs that are reliable or safe

slide-9
SLIDE 9

POT–9

Beizer’s testing levels on test process maturity

 Level 1

 Purpose of testing is to show that software works

 Level 0

 No difference between testing and debugging

slide-10
SLIDE 10

POT–10

Level 1

 Purpose of testing is to show that software works

 Significant step up

slide-11
SLIDE 11

POT–11

Level 1

 Purpose of testing is to show that software works

 Significant step up  But correctness is virtually impossible to either achieve or

demonstrate

slide-12
SLIDE 12

POT–12

Level 1

 Purpose of testing is to show that software works

 Significant step up  But correctness is virtually impossible to either achieve or

demonstrate

 Problems?

slide-13
SLIDE 13

POT–13

Level 1

 Purpose of testing is to show that software works

 Significant step up  But correctness is virtually impossible to either achieve or

demonstrate

 Run test suite with no failures  Is program correct?  Do we have bad tests?

slide-14
SLIDE 14

POT–14

Level 1

 Purpose of testing is to show that software works

 Significant step up  But correctness is virtually impossible to either achieve or

demonstrate

 Run test suite with no failures  Is program correct?  Do we have bad tests?

 Test engineers have no strict goal, real stopping rule or

formal test technique

slide-15
SLIDE 15

POT–15

Level 1

 Purpose of testing is to show that software works

 Significant step up  But correctness is virtually impossible to either achieve or

demonstrate

 Run test suite with no failures  Is program correct?  Do we have bad tests?

 Test engineers have no strict goal, real stopping rule or formal

test technique

 Test managers are powerless because they have no way to

quantitatively express or evaluate their work

slide-16
SLIDE 16

POT–16

Beizer’s testing levels on test process maturity

 Level 2

 Purpose of testing is to show that software doesn’t work

 Level 1

 Purpose of testing is to show that software works

 Level 0

 No difference between testing and debugging

slide-17
SLIDE 17

POT–17

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal

slide-18
SLIDE 18

POT–18

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal  Testers may like it but developers do not

slide-19
SLIDE 19

POT–19

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal  Testers may like it but developers do not  Why?

slide-20
SLIDE 20

POT–20

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal  Testers may like it but developers do not

 Level 1 thinking is natural for developers

slide-21
SLIDE 21

POT–21

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal  Testers may like it but developers do not

 Level 1 thinking is natural for developers

 What is the problem?

slide-22
SLIDE 22

POT–22

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal  Testers may like it but developers do not

 Level 1 thinking is natural for developers

 Have adversarial relationship

 Bad for team morale  Conflict of interest if the same person

slide-23
SLIDE 23

POT–23

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal  Testers may like it but developers do not

 Level 1 thinking is natural for developers

 Have adversarial relationship

 Bad for team morale  Conflict of interest if the same person

 What else?

slide-24
SLIDE 24

POT–24

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal  Testers may like it but developers do not

 Level 1 thinking is natural for developers

 Have adversarial relationship

 Bad for team morale  Conflict of interest if the same person

 What to do if no failures are found?

 Is software good?  Is testing bad?

slide-25
SLIDE 25

POT–25

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal  Testers may like it but developers do not

 Level 1 thinking is natural for developers

 Have adversarial relationship

 Bad for team morale  Conflict of interest if the same person

 What to do if no failures are found?

 Is software good?  Is testing bad?

 Conclusion?

slide-26
SLIDE 26

POT–26

Level 2

 Purpose of testing is to show that software doesn’t work

 Valid but negative goal  Testers may like it but developers do not

 Level 1 thinking is natural for developers

 Have adversarial relationship

 Bad for team morale  Conflict of interest if the same person

 What to do if no failures are found?

 Is software good?  Is testing bad?

 Having confidence when testing is complete is an important

goal

slide-27
SLIDE 27

POT–27

Beizer’s testing levels on test process maturity

 Level 3

 Purpose of testing is not to prove anything specific but to

reduce the risk of using the software

 Level 2

 Purpose of testing is to show that software doesn’t work

 Level 1

 Purpose of testing is to show that software works

 Level 0

 No difference between testing and debugging

slide-28
SLIDE 28

POT–28

Level 3

 Purpose of testing is not to prove anything specific but to

reduce the risk of using the software

 Realize that testing can show the presence of failures but

not their absence.

slide-29
SLIDE 29

POT–29

Level 3

 Purpose of testing is not to prove anything specific but to

reduce the risk of using the software

 Realize that testing can show the presence of failures but not

their absence.

 Accept fact that using software incurs some risk

slide-30
SLIDE 30

POT–30

Level 3

 Purpose of testing is not to prove anything specific but to

reduce the risk of using the software

 Realize that testing can show the presence of failures but not

their absence.

 Accept fact that using software incurs some risk

 May be small with unimportant consequences  May be big with important consequences, or even

catastrophic

slide-31
SLIDE 31

POT–31

Level 3

 Purpose of testing is not to prove anything specific but to

reduce the risk of using the software

 Realize that testing can show the presence of failures but not

their absence.

 Accept fact that using software incurs some risk

 May be small with unimportant consequences  May be big with important consequences, or even

catastrophic

 Entire team wants the same thing

slide-32
SLIDE 32

POT–32

Level 3

 Purpose of testing is not to prove anything specific but to

reduce the risk of using the software

 Realize that testing can show the presence of failures but not

their absence.

 Accept fact that using software incurs some risk

 May be small with unimportant consequences  May be big with important consequences, or even

catastrophic

 Entire team wants the same thing  Which is?

slide-33
SLIDE 33

POT–33

Level 3

 Purpose of testing is not to prove anything specific but to

reduce the risk of using the software

 Realize that testing can show the presence of failures but not

their absence.

 Accept fact that using software incurs some risk

 May be small with unimportant consequences  May be big with important consequences, or even

catastrophic

 Entire team wants the same thing

 Reduce the risk  Developer and tester work together

slide-34
SLIDE 34

POT–34

Beizer’s testing levels on test process maturity

 Level 4

 Testing is a mental discipline that helps all IT professionals

develop higher quality software

 Level 3

 Purpose of testing is not to prove anything specific but to reduce

the risk of using the software

 Level 2

 Purpose of testing is to show that software doesn’t work

 Level 1

 Purpose of testing is to show that software works

 Level 0

 No difference between testing and debugging

slide-35
SLIDE 35

POT–35

Level 4

 Testing is a mental discipline that helps all IT professionals

develop higher quality software

 Testing is a mental discipline that increases quality

slide-36
SLIDE 36

POT–36

Level 4

 Testing is a mental discipline that helps all IT professionals

develop higher quality software

 Testing is a mental discipline that increases quality  Testers become technical leaders of projects

slide-37
SLIDE 37

POT–37

Level 4

 Testing is a mental discipline that helps all IT professionals

develop higher quality software

 Testing is a mental discipline that increases quality  Testers become technical leaders of projects  Primary responsibility is measuring and improving software

quality

slide-38
SLIDE 38

POT–38

Level 4

 Testing is a mental discipline that helps all IT professionals

develop higher quality software

 Testing is a mental discipline that increases quality  Testers become technical leaders of projects  Primary responsibility is measuring and improving software

quality

 Improve the ability of developers to produce quality

software

slide-39
SLIDE 39

POT–39

Level 4

 Testing is a mental discipline that helps all IT professionals

develop higher quality software

 Testing is a mental discipline that increases quality  Testers become technical leaders of projects  Primary responsibility is measuring and improving software

quality

 Improve the ability of developers to produce quality

software

 Testers train developers

slide-40
SLIDE 40

POT–40

Level 4

 Example – spell checker

slide-41
SLIDE 41

POT–41

Level 4

 Example – spell checker

 Best purpose is to improve our ability to spell

slide-42
SLIDE 42

POT–42

Level 4

 Example – spell checker

 Best purpose is to improve our ability to spell

 Change of mindset

slide-43
SLIDE 43

POT–43

Level 4

 Example – spell checker

 Best purpose is to improve our ability to spell

 Change of mindset

 From – purpose is to find misspelled words