Project Delivery Process D784

D784 - Establish Testing Environment

DEFINITION

Establish a technical environment that promotes efficient, effective, and controlled execution of the entire testing program.

SUMMARY

The purpose of this activity is to design, develop, and implement the various aspects of the technical environment that are required for the entire testing program, including all types and levels of testing.  This activity includes installation of new tools, configuration of existing utilities and system software components, as well as development of custom software routines.

There are four main aspects:

• prepare testing environment
• install required test tools
• design testing support software
• develop testing support software.

PATH PLANNING GUIDANCE

Optional - required where a special testing environment is required or where testing tools or support software is required.

DEPENDENCIES

Prerequisites (Finish-Start):

• Testing Strategy from Delivery Approach Definition (S700/S710)

Prerequisites (Finish-Finish):

• Approach to Testing IP stage of testing processes (D800/D810)
• Working environment - Process D130

Dependent procedures (Finish-Start):

• Conducting the tests in the testing processes (D800/D810)

RECEIVABLES

• Testing Strategy from Delivery Approach Definition (S700/S710)
• Approach to Testing IPs from testing processes (D800/D810)
• Technical Plan IP (D110)
• Quality Plan (L080)

DELIVERABLES

• Test Environment Definition IP
• required testing environment(s)
• testing support software design
• testing support software

TOOLS

• various test tools

DETAILED DESCRIPTION OF TASKS

Prepare Testing Environment

Procure and implement facilities and equipment, as called for in the Testing Approach IP, which are necessary to support an efficient and effective testing process.

The purpose of this task is to prepare the technical environment for the entire testing process (all types and levels) by implementing the provisions defined in the detailed test plan for:

• platforms (mainframe resources, LAN servers, workstations, etc)
• communication/network facilities
• online storage capacity (on all appropriate platforms)
• source code management (libraries, version control, etc).

Worksteps:

• allocate test libraries
• work in conjunction with DBA or Administrator for test regions and data stores
• formalise procedures as required
• set up profiles for access and security (as required).

Information sources:

• Testing Approach IP
• site and vendor technical documentation
• site standards and procedures
• Testing Strategy (Delivery Approach Definition)
• test plan/scripts - Unit, Systems, Integration, User
• development procedures
• Quality Plan

The detailed definition may be presented in the Test Environment Definition IP containing:

• identification and configuration of platforms and networks
• allocation of CPU, DASD and communication resources
• names and definitions of libraries and other data sets
• security rules.

This task would address the entire testing process (all levels and types).

Responsibilities:

• Project Mgt - Ensures testing environment is established in a timely manner in relation to dependent project activities
• Tech Mgt - Performs technical support activities (security, data storage, equipment, platform and network configurations, etc) required to support the testing process
• Data Mgt - Performs data management activities (library allocation, database establishment and storage, etc) required to support the testing process
• Team/IR - Assists project manager in defining and documenting testing environment requirements

Install Required Test Tools

Provide tools in the test environment which were called for in the test plan by the time the initial stages of testing are scheduled to begin.  Test tools are not appropriate in all projects.  The approach will have been considered in the Testing Strategy of the Delivery Approach Definition (DAD) and the Testing Approach IP (D800)

The purpose of this task is to install, configure, and test all tools and utilities that will be used at any stage in the testing process.

Worksteps (for each tool):

• provide test tool requirements to proper installation person
• prepare environment for test tool installation
• install and configure tool
• document install procedures and prepare usage notes
• test the operational aspects of the tool.

Information sources:

• Testing Approach IP
• site and vendor technical documentation
• site standards and procedures
• Testing Strategy (Delivery Approach Definition)
• test plan/scripts - Unit, Systems, Integration, User Acceptance
• development procedures
• Test Environment Definition IP

The Test Environment Definition IP may be include:

• identification (including vendor, version, etc)
• description of role in the testing process
• configuration, parameters, etc.

This task would address the entire testing process (all levels and types).

The testing approach and plans may be amended if required (subject to appropriate change control).

Responsibilities:

• Project Mgt - Assists in identifying test tool requirements and ensures tools are installed in a timely manner in relation to dependent project activities
• Tech Mgt - Installs and configures system hardware or software tools required to support the testing process
• Data Mgt - Installs and configures database or application tools required to support the testing process
• Team/IR - Assists project manager in identifying test tool requirements

Design Testing Support Software

The purpose of this task is to design detailed specifications for the software that is to be developed specifically for this testing program.  Testing support software is not appropriate in all projects.  The overall approach will have been determined in the Testing Strategy of the Delivery Approach Definition (DAD) and the Testing Approach IP - see Process D800.

Software developed for this purpose commonly addresses the follow kinds of requirements:

• generating and managing test data (transactions and databases)
• tracking and controlling the testing process
• automatically recording, analysing and reporting test cases and results.

A specific custom development methodology is not prescribed by this methodology as it is normal to follow the user organisation’s standards wheresoever required.  Normally the agreed methods and standards will have been stated in the Quality Plan.

Worksteps:

• determine utility program requirements
• determine benefit associated with automated process
• develop specifications for test utility programs
• determine how these programs are to be utilised
• produce specifications for review
• finalise specifications.

Information sources:

• Testing Strategy IP
• site and vendor technical documentation
• site standards and procedures
• Testing Strategy (Delivery Approach Definition)
• test plan/scripts - Unit, Systems, Integration, User Acceptance
• development procedures
• Test Environment Definition IP.

The testing support software is designed.  The specification may contain:

• reference name or ID
• description of function and operation
• function flowchart showing inputs and outputs
• references to relevant detail technical design materials:
• layouts of records, transactions, reports, and screens
• database design and file structures
• explanation of specialised functions or calculations
• special testing requirements
• special software techniques to be used
• utilisation of common modules.

Analysis, design and construction is performed per individual software module in the form of complete technical specifications.

Responsibilities:

• Project Mgt - Reviews team members' work
• Team/IR - Designs software required to support and monitor application testing

Develop Testing Support Software

Produce robust, efficient, and effective software, based on the specifications in the previous step, that satisfies the testing automation requirements.

The purpose of this task is to:

• create and test the testing support software based on the design specifications developed by the previous task
• develop associated command level language required to operate the testing support programs.

Worksteps per module:

• review specifications
• write program code
• compile and debug to eliminate syntax errors
• test and debug to eliminate logic errors
• document completion and hand off to next step in the process.

Information sources:

• specifications from previous step
• Testing Strategy IP (D800)
• site and vendor technical documentation
• site standards and procedures
• Testing Strategy (Delivery Approach Definition)
• test plan/scripts - Unit, Systems, Integration, User Acceptance (D800)
• development procedures
• Test Environment Definition
• testing support software design (from previous step)
• Quality Plan

The testing support software is constructed.  Deliverables may include:

• documented source code
• executable code
• test cases and results
• associated command language procedures.

Responsibilities:

• Project Mgt - Reviews team members' work
• Team/IR - Develops software required to support and monitor application testing