configuration testing

© 2011 LogiGear Corporation. All Rights Reserved

Configuration TestingConfiguration Testing

THINGS YOU NEED TO KNOW


TABLE OF CONTENTTABLE OF CONTENT

Introduction Objectives Preconditions Testcases Bugs Tips & Tricks


IntroductionIntroduction

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.


ObjectivesObjectives

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


ObjectivesObjectives

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.


PreconditionsPreconditions

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.

http://www.opfro.org/Components/WorkUnits/Activities/Testing/UnitTesting.html


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.


Test CasesTest Cases

Test Case 1 Description: This use case describes the scenario of

booting with multiple displays



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



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



Test Case 2 Description This use case describes the scenario of

logging in with multiple displays


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


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


Bug CasesBug Cases

Bug 1: Configuration error with Mobile device


Bug CasesBug Cases

Bug 2: occurs with same ASP.NET version but on diff browsers


Tips & TricksTips & 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.


Tips and tricksTips 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.


ReferenceReference

.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.

configuration testing

Technology