Software Testing Day 1: Preliminaries

1
Software Testing Day 1 Preliminaries

• Aditya P. Mathur
• Purdue University
• August 12-16
• _at_ Guidant Corporation
• Minneapolis/St Paul, MN

Last update July 23, 2002
2
Class schedule

• Monday- August 12
• 8-830am Registration/Introductions
• 830-920 Lecture Session 1
• 920-930am Break
• 930-1030am Lecture Session 2
• 1030-1045am In-class exercises and discussion
• 1045-noon In-class exercises and discussion
• Noon-1pm Lunch
• 1-5pm Laboratory session (breaks as needed)

3
Class schedule-continued

• Tuesday-Thursday August 11-16
• 8-815am Review and QA
• 815-850am Lecture Session 1
• 850-9am Break
• 9-10am Lecture Session 2
• 10-1015am Break
• 1015-11am Lecture Session 3
• 11-noon In-class exercises and discussion
• Noon-1pm Lunch
• 1pm-5pm Laboratory (breaks as needed)

4
Class schedule-continued

• Friday August 16
• 8-815am Review and QA
• 815-850am Lecture Session 1
• 850-9am Break
• 9-10am Lecture Session 2
• 10-1015am Break
• 1015-11am Lecture Session 3
• 11-noon In-class exercises and discussion
• Noon-1pm Lunch
• 1pm-3pm Laboratory (breaks as needed)
• 3-4pm Participant survey and feedback
• 4-5pm Any pending items

5
Course Organization

• Part I Monday Preliminaries
• Part II Tuesday Functional Testing
• Part IIIWednesday Test Assessment and
  improvement
• Part IV Thursday Robustness, performance, and
  GUI testing
• Part V Friday Reliability and test process

6
Text and supplementary reading

• The craft of software testing by Brian Marick,
  Prentice Hall, 1995.
• Reading
• Supplied

7
Text and supplementary reading

• The combinatorial approach to automatic test data
  generation, D. Cohen et al., IEEE Software, VOL.
  13, NO. 5, September 1996, pp 83-87.
• Comparing the error detection effectiveness of
  mutation and data flow testing, in your notes,
  part III.

8
Text and supplementary reading

• Effect of test set minimization on the fault
  detection effectiveness of the all-uses
  criterion, in your notes, part III.
• Effect of test set size and block coverage on the
  fault detection effectiveness, in your notes,
  part III.