Introduction

Even the very best software testing process is nothing without the acceptance and consistent use by a community of testers within an organization. Technical issues aside, the introduction and adoption of a testing process is likely to be the most difficult step in providing a formal, rigorous, and re-usable process within an organization.

This chapter examines the issues involved in introducing a testing process into an organization and the management of its successful adoption and use. It also addresses the issues associated with the subsequent maintenance and update of the testing process.

Introduction and Adoption of a Testing Process

Overview

This section discusses the need to first establish that there is a requirement for a formal testing process within an organization, and where this is the case, examines the need to develop a strategy for the introduction and adoption of the process.

Establishing the Requirement

The first step in introducing a testing process within an organization is to establish that there is a requirement for such a process. In determining whether a particular organization has a requirement for a formal testing process, the following issues should be considered:

1. ▲ How much software testing does the organization conduct, and how frequently does testing take place? Clearly, if an organization performs very little testing and/or this task takes place infrequently, there will be a weak requirement for introducing a large-scale testing process and the associated infrastructure. However, there may still be significant benefit to be gained from documenting a standard approach to testing with some associated testing templates, to ensure that when testing does occur it is as consistent and economical as possible

2. […]