SE 754NT

1
SE 754-NT Object-Oriented Testing and
Reliability Robert Oshana Lecture
30 For more information, please
contact NTU Tape Orders NTU Media
Services [phone]
oshana_at_airmail.net
tapeorders_at_ntu.edu
2
Configuration testing

• Software Testing by Ron Patton
• Chapter 8

3
Configuration testing

• Making sure the software works with as many
  different hardware configurations as possible
• PC
• Components
• Peripherals
• Interfaces
• Options and memory
• Device drivers

4
(No Transcript)
5
(No Transcript)
6
(No Transcript)
7
Isolating configuration bugs

• Sure way to tell if a bug is a configuration bug
  (and not an ordinary bug) is to perform the
  exact same operation that caused the problem,
  step by step, on another computer with a
  different configuration
• Does the bug occur in the new environment?

8
Sizing up the job
9
Decide the types of HW you will need
10
Decide what HW brands, Models, and Device drivers
are available
11
Approaching the task

• Decide the types of HW you will need
• Decide what HW brands, Models, and Device drivers
  are available
• Decide which HW features, modes, options are
  possible
• Pare down the identified HW configurations to a
  manageable set

12
A number of possible configurations for a display
card
13
Approaching the task

• Identify your softwares unique features that
  will work with the HW configurations
• Design the test cases to run on each
  configuration
• Execute the tests on each configuration

14
Approaching the task

• Rerun the tests until the results satisfy your
  team

15
Obtaining the HW

• Buy only the configurations that you can run or
  will use most often
• Contact the HW manufacturer to lend or give HW
• Send a memo or email asking what HW is available
• If budget provides go to a compatibility test lab

16
SE 754-NT Object-Oriented Testing and
Reliability Robert Oshana End of
lecture For more information, please
contact NTU Tape Orders NTU Media
Services [phone]
oshana_at_airmail.net
tapeorders_at_ntu.edu