General Testing Background CISC 879 Spring 2007 Lori Pollock

Key Points * Software Testing versus Debugging? * Static versus Dynamic Testing? * Error -> Fault -> Failure - Not one-to-one * What is a bug? Error or Fault. * Kinds of faults: incorrect implementation vs omission vs surprise omission vs surprise

Test Cases  For a given Implementation under test (IUT): Pretest state Pretest state Test inputs or conditions Test inputs or conditions Expected outputs Expected outputs IUT: method, object, class, component, system  Levels of Testing: unit testing, integration testing, system testing Interesting test case – good chance of revealing a fault. Test Strategy – heuristic/algorithm to create test cases Test Design – create a test suite with a test strategy

Traditional Software Testing Process Oracle Pass/ Fail Replay Tool Test Cases Test Cases Actual Results Expected Results Application Specification Test Case Generator Application Representation Application Implementation

Kinds of Testing 1. Fault-directed: intended to reveal faults through failures (unit/integration) 2. Conformance-based: intended to show conformance with required capabilities (system) Today’s paper and talks – test designs