Artifact: Test Environment Configuration |
This work product specifies an arrangement of hardware, software, and associated environment settings that are required to enable accurate tests to be conducted, which tests will evaluate one or more target test items.
Purpose
The purpose of the test environment configuraiton is to help ensure that: The results of testing activities are accurate and valid Testing activities have a higher likelihood of being systematically reproduced
Relationships
Container Artifact | Test Architecture
Roles | Responsible: | Modified By: Test Designer
Tasks | Input To: Structure Test Environment Configuration | Output From: Define Test Strategy Structure Test Environment Configuration
Description
Main Description | Each Test Environment Configuration specificies an appropriate, controlled setting in which to conduct the required test and evaluation activities. Providing a controlled environment, built from a known configuration in which to conduct these activities, helps to ensure that the results of these efforts are accurate, valid, and have a higher likelihood of being systematically reproduced. A well-controlled Test Environment is an important aspect of efficient failure analysis and fault resolution.
Brief Outline | Each Test Environment Configuration should consider various aspects of testing, including the following: The basic computer hardware requirements (for example, processors, memory storage, hard-disk storage, input/output interface devices The basic underlying software environment (for example, operating system and the basic productivity tools, such as e-mail, calendar, and so on) Additional specialized input/output peripheral hardware (for example, bar-code scanners, receipt printers, cash draws, sensor devices, and so on) The required software for the specialized input/output peripheral hardware (for example, drivers, and interface and gateway software) The minimal set of software tools necessary to facilitate test, evaluation, and diagnostic activities (for example, memory diagnostics, automated test execution, and so on) The required configuration settings of both hardware and software options (for example, video-display resolution, resource allocation, environment variables, and so on) The required pre-existing consumables (for example, populated data sets, receipt printer dockets, and so on)
Illustrations
Reports | Environment Specification
Tailoring
Impact of not having | Without this artifact, results may be inconsistent or not repeatable because: There is no record of the environment at the time of test. The same components are not used, or are not used consistently, especially test tools. The architects and implementers of the environment have failed to transfer the knowledge of it to the operators and testers. Test environment issues may force testing to be executed in other environments, in competition with other teams and projects. For instance, in the development environment, test results can be unpredictable for inexplicable reasons due to the instability of this environment. In the worst case, testing is executed in the production environment where the risk to the business can be significant. Additionally, the test resources expended and the duration will likely extend because: The required components will not be available when needed; they may be absent, insufficient or the wrong ones. There is a lack of documentation to support efficient on-going support and operation of the test environment.
Reasons for not needing | If a fully configured and robust test environment, known to provide all required resources, already exists and supports the testing requirements, the full version of this work product may not be necessary. However, even if it does exist, the process of reviewing its documentation may serve to identify missing components for this particular project or other omitted aspects of this work product, such as schedule, data management processes, and processes for the preservation of the test results. Small projects would only need to produce a subset of the information.
Representation Options | Where possible, attempt to keep the total number of unique Test Environment Configurations to a minimum, and to a manageable level. This can be achieved by consolidating similar environments, typically where similar base hardware and software profiles are used, with only minor differences existing in the configuration settings. However, be careful not to consolidate Test Environment Configurations to the point of invalidating the integrity and purpose of each configuration. We recommend the use of hard-disk imaging tools that allow Test Environment Configurations to be backed up and easily restored. Also consider using removable or swappable hard drives to further improve accuracy and efficiency.
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.