1. Comment on Testing & Test Case Generation
Consider your “motivations” for testing:
(positive) Show that the system WORKS
(negative) FIND as much DEFECTS as possible before release
Consider potential testing goals:
Test cases cover all the requirements; just the major requirements; some combination of major/minor requirements
Test cases cover all the possible paths; just major paths; some combination of major/minor logical paths.
Consider when would you stop testing:
All test cases executed and all bugs fixed
All test cases executed and all major bugs fixed
Some part of test cases (e.g. 80%) tested and all bugs fixed

2. Example: Defining/Tracking Test Cases by Requirements
Description
Expected
result
Req
Test status/result
Test 1.1: key in
proj Id & descrip
and press “enter’
Req 1: -----
Proj id and
descrip in the
db fields
Executed- pass
Executed - failed ; neg
Id accepted; reported sev 2;
(waiting for fix & retest)
Test 1.2: key in
“negative” proj id
Error message
Req 2: ----
Test 2.1:
Planned exec: 11/22/2012