1 / 8

Integration between reviews and testing

Integration between reviews and testing. Hans Schaefer Hans.Schaefer@ieee.org. Can you save test work after inspections? Self assessment about how you do inspections. Can you cut down test after good reviews and inspections?. Can you rely on inspections alone? What is a good inspection?

fergal
Télécharger la présentation

Integration between reviews and testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integration between reviews and testing Hans Schaefer Hans.Schaefer@ieee.org Can you save test work after inspections? Self assessment about how you do inspections

  2. Can you cut down test after good reviews and inspections? • Can you rely on inspections alone? • What is a good inspection? • How to know? • What to cut down?

  3. Can you rely on inspections alone? • NO! • You need to measure the FINAL quality. • Test finds issues inspections don't find well: • Issues that are hidden in the connections between many parts. • Performance problems • New errors introduced after inspection • Surviving errors

  4. Cleanroom Software Engineering and Testing • Cleanroom heavily relies on inspections. • Inspections replace unit test. System test replaced by statistical usage testing (software reliability engineering). • Reasoning: • ”If you have no chance to test your unit, you will de better inspections!” • But: This has never been verified in large projects. • Conclusion: Cleanroom PLUS traditional testing!

  5. What is a good inspection? • The right (qualified) people attended • They had time to prepare • Well led meeting • 3 to 7 people • Meeting in chunks of <= 2 hours • Material met entry criteria • Check lists • Concentration on MAJOR issues • Follow up of issues found • People know inspection technique • Defect detection percentage known • Assess yourself!

  6. How to know inspections were good enough? And the results as well? • Inspection database • Check against other inspections • Experience in how testing goes after good inspections - in YOUR organization! • Experience in which defects disappear from testing

  7. What you can cut down after inspections • Defect repair time during testing • Test re-execution (less faults require less repairs and regression test) • Getting the test to execute at all (Start trouble) • Some, but not all unit testing • Other testing only after experience data available • Do more test where inspection found many defects!

  8. Danger • If an inspection finds few defects: • Maybe the software is good? • Maybe the inspection was bad?

More Related