Configuration testing

427 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
427
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Configuration testing

  1. 1. © 2011 LogiGear Corporation. All Rights ReservedConfiguration TestingTHINGS YOU NEED TO KNOW
  2. 2. © 2011 LogiGear Corporation. All Rights ReservedTABLE OF CONTENT Introduction Objectives Preconditions Testcases Bugs Tips & Tricks
  3. 3. © 2011 LogiGear Corporation. All Rights ReservedIntroduction Configuration testing is the system testingof different variations of anintegrated, blackbox application against itsconfigurability requirements. The typical goals of configuration testingare to:Cause the application to fail to meet itsconfigurability requirements so that theunderlying defects can beidentified, analyzed, fixed, and prevented in thefuture.
  4. 4. © 2011 LogiGear Corporation. All Rights ReservedObjectives The typical objectives of configurationtesting are to:Partially validate the application (i.e., todetermine if it fulfills its configurabilityrequirements).Cause failures concerning the configurabilityrequirements that help identify defects that arenot efficiently found during unit and integrationtesting:• Functional Variants.• Internationalization (e.g., multiplelanguages, currencies, taxes and tariffs, timezones, etc.).• Personalization
  5. 5. © 2011 LogiGear Corporation. All Rights ReservedObjectivesReport these failures to the developmentteams so that the associated defects canbe fixed.Determine the effect of adding ormodifying hardware resources such as:• Memory• Disk and tape resources• Processors• Load balancersDetermine an optimal systemconfiguration.
  6. 6. © 2011 LogiGear Corporation. All Rights ReservedPreconditions Configuration testing can typicallybegin when the followingpreconditions hold:The configurability requirements to betested have been specified.Multiple variants of the application exist.The relevant software components havepassed unit testing.
  7. 7. © 2011 LogiGear Corporation. All Rights ReservedSoftware integration testing has started.However, configuration testing can beginprior to the distribution of the softwarecomponents onto the hardwarecomponents.The relevant system components havepassed system integration testing.The independent test team is adequatelystaffed and trained in configurationtesting.The test environment is ready.
  8. 8. © 2011 LogiGear Corporation. All Rights ReservedTest Cases Test Case 1 Description:This use case describes the scenario ofbooting with multiple displays
  9. 9. © 2011 LogiGear Corporation. All Rights ReservedTest Cases How to testTurn your computer off (most likely alaptop in this scenario)Plug in an external monitorTurn your computer on againWatch the boot sequence up to the loginscreen
  10. 10. © 2011 LogiGear Corporation. All Rights ReservedTest Cases Expected ResultIgnore the external displayClone the displays if they have thesame dimensionsTreat the displays as one big screenwith the Fedora logo appearing on oneof the monitors
  11. 11. © 2011 LogiGear Corporation. All Rights ReservedTest Cases Test Case 2 DescriptionThis use case describes the scenario oflogging in with multiple displays
  12. 12. © 2011 LogiGear Corporation. All Rights Reserved How to testLog outOn the login screen, change the displayconfiguration• If an external monitor was plugged in,unplug it• If no external monitor was plugged in, plugone in nowLog in
  13. 13. © 2011 LogiGear Corporation. All Rights Reserved Expected ResultThe login screen should handle the displayconfiguration change reasonably, e.g.Ignore the external displayClone the monitors if they have the samedimensionsTreat the monitors as one big screen with thelogin screen appearing on one of the monitorsMove the greeter to the remaining screen if themonitors it was on gets unplugged
  14. 14. © 2011 LogiGear Corporation. All Rights ReservedBug Cases Bug 1: Configuration error withMobile device
  15. 15. © 2011 LogiGear Corporation. All Rights ReservedBug Cases Bug 2: occurs with same ASP.NETversion but on diff browsers
  16. 16. © 2011 LogiGear Corporation. All Rights ReservedTips & Tricks If you are starting for theconfiguration testing on a piece ofsoftware, we need to consider whichof these configuration areas would bemost closely tied to the program.
  17. 17. © 2011 LogiGear Corporation. All Rights ReservedTips and tricksA highly graphical computer game willrequire lots of attention to the video andsound areasA greeting card program will beespecially vulnerable to printer issuesA fax of communications program willneed to be tested with numerousmodems and network configuration.
  18. 18. © 2011 LogiGear Corporation. All Rights ReservedReference .http://www.allinterview.com/showanswers/56412/page2.html. .http://www.opfro.org/index.html?Components/WorkUnits/Activities/Testing/ConfigurationTesting.html~Contents. .http://fedoraproject.org/wiki/QA:Testcase_Display_Configuration_Login.

×