Test Management

Purpose
It is the role of test management to ensure that new or modified service products meet the business requirements for which they have been developed or enhanced.

The purpose of test management is to ensure that a testing strategy is both devised and applied that is efficient, effective and economic.

The testing strategy should define the objectives of all test stages and the techniques that apply. The testing strategy also forms the basis for the creation of a standardised documentation set, and facilitates communication of the test process and its implications outside of the test discipline. Any test support tools introduced should be aligned with, and in support of, the test strategy.

Test management is also concerned with both test resource and test environment management.

Key elements of test management include:

• Test organisation -the set-up and management of a suitable test organisational structure and explicit role definition. The project framework under which the testing activities will be carried out is reviewed, high-level test phase plans prepared and resource schedules considered. Test organisation also involves the determination of configuration standards and the definition of the test environment.
• Test planning - the requirements definition and design specifications facilitate in the identification of major test items and these may necessitate the test strategy to be updated. A detailed test plan and schedule is prepared with key test responsibilities being indicated.
• Test specifications - required for all levels of testing and covering all categories of test. The required outcome of each test must be known before the test is attempted.
• Unit, integration and system testing - configuration items are verified against the appropriate specifications and in accordance with the test plan. The test environment should also be under configuration control and test data and results stored for future evaluation.
• Test monitoring and assessment - ongoing monitoring and assessment of the integrity of the development and construction. The status of the configuration items should be reviewed against the phase plans and test progress reports prepared providing some assurance of the verification and validation activities.
• Product assurance - the decision to negotiate the acceptance testing programme and the release and commissioning of the service product is subject to the "product assurance" role being satisfied with the outcome of the verification activities. Product assurance may oversee some of the test activity and may participate in process reviews.

Fitness for purpose checklist:
Is there a documented test strategy that defines the objectives of all test stages and the techniques that may apply, e.g. non-functional testing and the associated techniques such as performance, stress and security etc?

Does the test plan prescribe the approach to be taken for intended test activities, identifying:

• the items to be tested
• the testing to be performed
• test schedules
• resource and facility requirements
• reporting requirements
• evaluation criteria
• risks requiring contingency measures?

Are test processes and practices reviewed regularly to assure that the testing processes continue to meet specific business needs?

For example, e-commerce testing may involve new user interfaces and a business focus on usability may mean that the organisation must review its testing strategies

Notes:
A common criticism of programmes containing development or construction elements is that insufficient time is allocated to the testing and commissioning of the construct and its supporting systems and services. Testing and commissioning is often inadequately considered by project teams and is pressurised by available time and resources particularly towards project completion.

It is essential that sufficient time and suitable resources are dedicated to testing and commissioning to assure the fundamental success of the project. There are advantages in using dedicated, specialist resources i.e. independent of the development / construction team and the project sponsor should ensure that testing requirements are considered throughout the project lifecycle and a suitable test strategy and appropriate test plans are formulated and instantiated.

Source information:

• Business requirements including success criteria.
• Project plans including detailed phase/stage plans and schedules.
• Requirements definition.
• Design specification.
• Operability standards.
• Implementation strategy and release plans.
• Customer acceptance criteria.
• Customer acceptance test specification.