1 / 17

Chapter 18 Software Testing Strategies

Chapter 18 Software Testing Strategies. Testing Strategy. unit test. integration test. system test. validation test. Unit Testing. module to be tested. results. software engineer. test cases. Unit Testing. module to be tested. interface. local data structures.

abril
Download Presentation

Chapter 18 Software Testing Strategies

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. Chapter 18Software Testing Strategies

  2. Testing Strategy unit test integration test system test validation test

  3. Unit Testing module to be tested results software engineer test cases

  4. Unit Testing module to be tested interface local data structures boundary conditions independent paths error handling paths test cases

  5. Unit Test Environment driver interface local data structures Module boundary conditions independent paths error handling paths stub stub test cases RESULTS

  6. Integration Testing Strategies • Options: • • the “big bang” approach • • an incremental construction strategy

  7. Top Down Integration A top module is tested with stubs B F G stubs are replaced one at a time, "depth first" C as new modules are integrated, some subset of tests is re-run D E

  8. Bottom-Up Integration A B F G drivers are replaced one at a time, "depth first" C worker modules are grouped into builds and integrated D E cluster

  9. Sandwich Testing A Top modules are tested with stubs B F G C Worker modules are grouped into builds and integrated D E cluster

  10. High Order Testing validation test system test alpha and beta test other specialized testing

  11. Debugging: A Diagnostic Process

  12. The Debugging Process test cases results new test cases regression tests suspected causes Debugging corrections identified causes

  13. Debugging Effort time required to diagnose the symptom and determine the cause time required to correct the error and conduct regression tests

  14. Symptoms & Causes symptom and cause may be geographically separated symptom may disappear when another problem is fixed cause may be due to a combination of non-errors cause may be due to a system or compiler error cause may be due to symptom assumptions that everyone cause believes symptom may be intermittent

  15. Consequences of Bugs infectious damage catastrophic extreme serious disturbing annoying mild Bug Type Bug Categories: function-related bugs, system-related bugs, data bugs, coding bugs, design bugs, documentation bugs, standards violations, etc.

  16. Debugging Techniques brute force / testing backtracking induction deduction

  17. Debugging: Final Thoughts 1. Don't run off half-cocked, think about the symptom you're seeing. 2. Use tools (e.g., dynamic debugger) to gain more insight. 3. If at an impasse, get help from someone else. 4. Be absolutely sure to conduct regression tests when you do "fix" the bug.

More Related