b. Approaching the Task( 1) The following general process that you should use when planning e your configuration testing 383 1 ) Decide the types of hardware you will need Look closely a your software feature set to make sure that you cover verything 2 )Decide what hardware brands, models, and device drivers are available Work with your sales and marketing people to create a list of hardware to test with. If they can not or won,t help, grab some recent editions and back issues of some information to get an idea of what hardware is available and what is popular Do some research to see if some of devices are clones of each other and therefore equivalent-falling under the same equivalence partition
16 b. Approaching the Task (1) The following general process that you should use when planning your configuration testing. 1.) Decide the types of hardware you will need. Look closely a your software feature set to make sure that you cover everything. 2.) Decide what hardware brands, models, and device drivers are available. Work with your sales and marketing people to create a list of hardware to test with. If they can not or won’t help, grab some recent editions and back issues of some information to get an idea of what hardware is available and what is popular. Do some research to see if some of devices are clones of each other and therefore equivalent-falling under the same equivalence partition. Zhu.Kerry@gmail.com
N b. Approaching the Task(2) ① 3)Decide which hardware features, modes, and options are possible 8 Every device has options, and your software may not need to 3 support all of them. a good example of this is computer games 4)Pare down the identified hardware configurations to a manageable set Given that you do not have the time or budget to test everything you need to reduce the thousands of potential configurations into the ones that matter-the ones you are going to test
17 b. Approaching the Task (2) 3) Decide which hardware features, modes, and options are possible. Every device has options, and your software may not need to support all of them. A good example of this is computer games. 4) Pare down the identified hardware configurations to a manageable set. Given that you do not have the time or budget to test everything, you need to reduce the thousands of potential configurations into the ones that matter—the ones you are going to test. Zhu.Kerry@gmail.com
b. Approaching the Task(3) N天2 Ultimately, the decision-marking process that you use to equivalence partition e the configurations into smaller sets is up to you and your team. There is no (g right formula. Every software project is different and will have different B selection criteria. Just make sure that everyone on the project team, especially your project manager, is aware of what configurations are being tested and g what variables went into selecting them For example Popularity Device/driver (1=most, 10=least)I( Laser/InkJet) (years)I Manufacturer Model version Options Laser 3 HAL Printers LDIY2000 1.0 B/W Draft Quality Colo Draft Quality Ink jet HAL Printers LDIY2000 1.0a B/W Draft Qualit Colo Art/photo Inkjet HAL Printers LDIY2000 2.0 B Draft Quali 100d 200d Laser Okee DohKee LJ100 1.5 B/W 300g 2 2 OkeeDohkee EasyPrint 1.0 Auto 6000dpi
18 b. Approaching the Task (3) Ultimately, the decision-marking process that you use to equivalence partition the configurations into smaller sets is up to you and your team. There is no right formula. Every software project is different and will have different selection criteria. Just make sure that everyone on the project team, especially your project manager, is aware of what configurations are being tested and what variables went into selecting them. For example: 1 Laser 3 HAL Printers LDIY2000 1.0 B/W Draft Quality 5 InkJet 1 HAL Printers LDIY2000 1.0a Color B/W Draft Quality Draft Quality 5 InkJet 1 HAL Printers LDIY2000 2.0 Color B/W Art / Photo Draft Quality 10 Laser 5 OkeeDohKee LJ100 1.5 B/W 100dpi 200dpi 300dpi 2 InkJet 2 OkeeDohKee EasyPrint 1.0 Auto 6000dpi Model Device/Driver version Options Popularity (1=most,10=least) Type (Laser/InkJet) Age (years) Manufacturer Zhu.Kerry@gmail.com
b. Approaching the Task (4) N天2⑧ 5 ) Identify your software unique features that work with the hardware configurations B The key word here is unique. You do not want to, nor do you need to completely test your software on each configuration You need to test only E Document WordPad those features that are fle Edt View Insert Format Help different from each 自口舀岛吗 other that interact with simSun 13 Westem B∠u the hardware 8……1,,,;…2…34 For example RED Blue Green Hello, this is test Good Afternoon For Help, press F1
19 b. Approaching the Task (4) 5.) Identify your software unique features that work with the hardware configurations. The key word here is unique. You do not want to, nor do you need to, completely test your software on each configuration. You need to test only those features that are different from each other that interact with the hardware. For example: Zhu.Kerry@gmail.com
b. Approaching the Task (5) N天2⑧ 6 )Design the test cases to run on each configuration. a. Select and set up the next test configuration from the list 383 b. Start the software C. Load in the file test. doc d. Confirm that the displayed file is correct e. Print the document Confirm that there are no error messages and that the printed document matches the standard g. Log any discrepancies as a bug In reality, the steps would be much more involved, including more detail and specifics on exactly what to do
20 b. Approaching the Task (5) 6.) Design the test cases to run on each configuration. a. Select and set up the next test configuration from the list. b. Start the software. c. Load in the file test.doc d. Confirm that the displayed file is correct. e. Print the document. f. Confirm that there are no error messages and that the printed document matches the standard. g. Log any discrepancies as a bug. In reality, the steps would be much more involved, including more detail and specifics on exactly what to do. Zhu.Kerry@gmail.com