COMP 4004 Lecture Notes - Lecture 4: Control Flow Graph, Execution Model, Control Flow

• School: Carleton University
• Department: Computer Science
• Course: COMP 4004
• Professor: Jean-Pierre Corriveau

Document Summary

This pattern represents these relationships as a decision table: to use eucs we need to determine operational variables, operational variables are inputs, outputs, and environment conditions that: Lead to (cid:862)significantly different(cid:863) paths of a use case: abstract the state of the system under test, result in (cid:862)significantly different(cid:863) system responses, typical expected faults, domain faults: usually on boundary of conditions, ex. Logic faults: logic of specification is incorrectly coded: ex. Incorrect or missing dependency on pre-conditions: a uc behaves correctly despite a violated pre-condition, ex. Expired card works: undesirable feature interactions (or is it scenario interactions, ex. Atm shut downs while user is doing a transaction! Incorrect output: ex. wrong balance, abnormal termination, ex. Atm eats your card: omissions and surprises, ex. Pin does not get validated, all your accounts are zeroed: choosing operational variables is an art, determining how manageable your test plan is.