1. © 2011 LogiGear Corporation. All Rights Reserved
Configuration Testing
THINGS YOU NEED TO KNOW

2. © 2011 LogiGear Corporation. All Rights Reserved
TABLE OF CONTENT
 Introduction
 Objectives
 Preconditions
 Testcases
 Bugs
 Tips & Tricks

3. © 2011 LogiGear Corporation. All Rights Reserved
Introduction
 Configuration testing is the system testing
of different variations of an
integrated, blackbox application against its
configurability requirements.
 The typical goals of configuration testing
are to:
Cause the application to fail to meet its
configurability requirements so that the
underlying defects can be
identified, analyzed, fixed, and prevented in the
future.

4. © 2011 LogiGear Corporation. All Rights Reserved
Objectives
 The typical objectives of configuration
testing are to:
Partially validate the application (i.e., to
determine if it fulfills its configurability
requirements).
Cause failures concerning the configurability
requirements that help identify defects that are
not efficiently found during unit and integration
testing:
• Functional Variants.
• Internationalization (e.g., multiple
languages, currencies, taxes and tariffs, time
zones, etc.).
• Personalization

5. © 2011 LogiGear Corporation. All Rights Reserved
Objectives
Report these failures to the development
teams so that the associated defects can
be fixed.
Determine the effect of adding or
modifying hardware resources such as:
• Memory
• Disk and tape resources
• Processors
• Load balancers
Determine an optimal system
configuration.

6. © 2011 LogiGear Corporation. All Rights Reserved
Preconditions
 Configuration testing can typically
begin when the following
preconditions hold:
The configurability requirements to be
tested have been specified.
Multiple variants of the application exist.
The relevant software components have
passed unit testing.

7. © 2011 LogiGear Corporation. All Rights Reserved
Software integration testing has started.
However, configuration testing can begin
prior to the distribution of the software
components onto the hardware
components.
The relevant system components have
passed system integration testing.
The independent test team is adequately
staffed and trained in configuration
testing.
The test environment is ready.

8. © 2011 LogiGear Corporation. All Rights Reserved
Test Cases
 Test Case 1 Description:
This use case describes the scenario of
booting with multiple displays

9. © 2011 LogiGear Corporation. All Rights Reserved
Test Cases
 How to test
Turn your computer off (most likely a
laptop in this scenario)
Plug in an external monitor
Turn your computer on again
Watch the boot sequence up to the login
screen

10. © 2011 LogiGear Corporation. All Rights Reserved
Test Cases
 Expected Result
Ignore the external display
Clone the displays if they have the
same dimensions
Treat the displays as one big screen
with the Fedora logo appearing on one
of the monitors

11. © 2011 LogiGear Corporation. All Rights Reserved
Test Cases
 Test Case 2 Description
This use case describes the scenario of
logging in with multiple displays

12. © 2011 LogiGear Corporation. All Rights Reserved
 How to test
Log out
On the login screen, change the display
configuration
• If an external monitor was plugged in,
unplug it
• If no external monitor was plugged in, plug
one in now
Log in

13. © 2011 LogiGear Corporation. All Rights Reserved
 Expected Result
The login screen should handle the display
configuration change reasonably, e.g.
Ignore the external display
Clone the monitors if they have the same
dimensions
Treat the monitors as one big screen with the
login screen appearing on one of the monitors
Move the greeter to the remaining screen if the
monitors it was on gets unplugged

14. © 2011 LogiGear Corporation. All Rights Reserved
Bug Cases
 Bug 1: Configuration error with
Mobile device


15. © 2011 LogiGear Corporation. All Rights Reserved
Bug Cases
 Bug 2: occurs with same ASP.NET
version but on diff browsers

16. © 2011 LogiGear Corporation. All Rights Reserved
Tips & Tricks
 If you are starting for the
configuration testing on a piece of
software, we need to consider which
of these configuration areas would be
most closely tied to the program.

17. © 2011 LogiGear Corporation. All Rights Reserved
Tips and tricks
A highly graphical computer game will
require lots of attention to the video and
sound areas
A greeting card program will be
especially vulnerable to printer issues
A fax of communications program will
need to be tested with numerous
modems and network configuration.

18. © 2011 LogiGear Corporation. All Rights Reserved
Reference
 .http://www.allinterview.com/showan
swers/56412/page2.html.
 .http://www.opfro.org/index.html?Co
mponents/WorkUnits/Activities/Testin
g/ConfigurationTesting.html~Content
s.
 .http://fedoraproject.org/wiki/QA:Tes
tcase_Display_Configuration_Login.