1 test10b Software Testing Necessary to measure and certify quality in software

2 test10b Why Software Testing? u Shows actual behavior of software –proofs are based on abstraction –proofs may have errors u May use 20% of total development effort –important to make good use of effort –testers often don’t make good selection of tests u Can not do exhaustive testing

3 test10b Terminology (IEEE Glossary) u Failure –external behavior is incorrect u Fault –discrepancy in code that causes a failure u Error –1. Human mistake that caused fault –2. All of above

4 test10b Fault, Failure, or Error? u A. returns wrong value u B. forgot a special case u C. If (a = b) in C++

5 test10b Test Phase Matching u Component u Integration u System u Acceptance u Performance of whole system u Interfaces u User u Modules

6 test10b Test Plans u Specified during requirement phase u Based on requirements –Black Box Testing

7 test10b Class Discussion u What are the advantages of test plans written right after the requirements are available?

8 test10b IEEE Standard for Software Test Documentation IEEE Std

11 test10b partial contents of a Test Plan (IEEE Standard) u identifier u introduction u test items (what is to be tested) u features –to be tested –not to be tested u methodology u pass/fail criteria u suspension criteria u deliverables u responsibilities u schedule u contingency plans u approvals

12 test10b Other test documents u test-case specification –inputs, outputs, procedures u test-procedure specification u test log u test-incident report u test-summary report

13 test10b L10bS11 - Individual Task u Write a test plan for B&B software –Any section that you feel is not applicable, write n/a u 15 pts, due Tuesday, 9am (on and off)

Questions