Closing words on V - PowerPoint PPT Presentation

1 / 10
About This Presentation
Title:

Closing words on V

Description:

When a bug is found by testing, it means that earlier phases of ... The testing group finds 38 faults, 8 of which were seeded. How many unseeded faults remain? ... – PowerPoint PPT presentation

Number of Views:17
Avg rating:3.0/5.0
Slides: 11
Provided by: stever155
Category:

less

Transcript and Presenter's Notes

Title: Closing words on V


1
Closing words on VV
  • Testing is our last line of defense against
    bugs, not the first or only line of defense. When
    a bug is found by testing, it means that earlier
    phases of our software development process are
    wanting.
  • I dont see testing actually disappearing
    because the remaining bugs are always subtler and
    nastier.
  • Bezier

2
Why IVV Group?
  • Protect Testers and provide objectivity
  • Configuration compatibility testing
  • Performance and throughput testing
  • Network testing
  • Localization
  • Risk reduction and safety-critical software

3
Why IVV Group?
  • Protect testers and provide objectivity
  • Protect testers from political influence
  • Allow testers to be objective, independent of
    programmers

4
Why IVV Group?
  • Configuration compatibility testing
  • Difficult for developers to stay aware of all
    nuances of different environments
  • Independent group can stay aware
  • Group may run different tests than developers

5
Why IVV Group?
  • Performance and throughput testing
  • Not an issue in most software products
  • Where it is an issue, special tools are needed

6
Why IVV Group?
  • Network testing
  • Special case of configuration testing

7
Why IVV Group?
  • Localization
  • Some products are specialized to location (e. g.
    language versions or country-specific
    regulations)
  • Similar issues to configuration compatability

8
Why IVV Group?
  • Risk reduction and safety-critical software
  • Legal issues an independent group may reduce
    legal exposure
  • IVV group should not just repeat previous tests

9
Fault Seeding
  • Estimate the number of faults in a program
  • Seed (add) errors to code
  • Assume that the likelihood of finding any error
    is the same
  • Then
  • Detected Seeded/total seeded
  • detected nonseeded/total nonseeded

10
Example
  • We seed 20 faults in a system.
  • The testing group finds 38 faults, 8 of which
    were seeded.
  • How many unseeded faults remain?
Write a Comment
User Comments (0)
About PowerShow.com