Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Objectives
Configuration testing and compatibility testing are two testing processes that are often ignored in many project teams. In this lecture we will explore:
What is configuration testing Configuration testing steps What is compatibility testing Compatibility testing steps
2009, CMU-ISR
2009, CMU-ISR
2009, CMU-ISR
Steps
2009, CMU-ISR
there should be 350*200*800*1200 combinations You may conduct a certain number of test cases on these different configurations. The number of total test cases could be larger.
2009, CMU-ISR
2009, CMU-ISR
Determine what hardware brands, models and device drivers are available.
Determine proper devices Identify equivalent devices Determine device drivers included with:
1. Operation system 2. The device 3. Latest drivers available for the hardware or operating system
2009, CMU-ISR
2009, CMU-ISR
10
Approach
2009, CMU-ISR
11
Suggestions
You may adopt the following:
Identifying hardware standards to help you get deep insight about the hardware so that you can make more informed equivalence partition decisions. Answering the following questions may help you when performing configuration testing. 1. What external hardware will operate with this software? 2. What models and versions of that hardware are available? 3. What features or options does that hardware support?
2009, CMU-ISR
12
2009, CMU-ISR
13
Approach
Perform the exact same operation that caused the problem, step by step on another computer with a different hardware setup. If the defect doesnt occur, it may be that you have a configuration problem.
2009, CMU-ISR 14
Solution
Under the first situation, it is surely your responsibility to fix the defect. Under the second situation: The hardware vendor fixes the defect, or Provides a software version to get around the hardware defect.
2009, CMU-ISR 15
Compatibility testing is a test process much like configuration testing. It takes care of interactions with compatible software which should be defined in the specification. The software may interact with each other. If the interaction fails, of course, the function will also fail.
2009, CMU-ISR
16
Steps
2009, CMU-ISR
17
2009, CMU-ISR
18
2009, CMU-ISR
20
2009, CMU-ISR
21
Other Steps
About the remaining steps:
Design test cases for each compatible software. Conduct the tests. Fix defects and verify modifications. Report results. These steps are much like that of configuration testing. You can refer to previous slides.
2009, CMU-ISR
22
Summary
Configuration testing and compatibility testing are two similar testing processes. Configuration testing supports hardware while compatibility testing supports software. Many project teams combine configuration testing with compatibility testing. The common steps of the two testing processes are: 1. Identify needed hardware/software 2. Design test cases 3. Run test cases 4. Fix defects and verify modifications 5. Report results
2009, CMU-ISR
23