ITIL Testing Process Management Plan and Testing Strategy Templates

Download Free ITIL Testing Process Management Plan and Testing Strategy Templates

Testing Process Management Plan Templates can be used as SDLC (Software Development Lifecycle Process) Review or Improvement Process
Introduction
This test approach document describes the appropriate strategies, process, workflows and methodologies used to plan, organize, execute and manage testing of software projects within caBIG.

Scope
Describe the current test approach scope based on your role and project objectives.

In Scope
The caBIG Test Plan defines the unit, integration, system, regression, and Client Acceptance testing approach. The test scope includes the following:
- Testing of all functional, application performance, security and use cases requirements listed in the Use Case document.
- Quality requirements and fit metrics.
- End-to-end testing and testing of interfaces of all systems that interact with the .

Quality Objective
Primary Objective
A primary objective of testing application systems is to: assure that the system meets the full requirements, including quality requirements (AKA: Non-functional requirements) and fit metrics for each quality requirement and satisfies the use case scenarios and maintain the quality of the product. At the end of the project development cycle, the user should find that the project has met or exceeded all of their expectations as detailed in the requirements.

Any changes, additions, or deletions to the requirements document, Functional Specification, or Design Specification will be documented and tested at the highest level of quality allowed within the remaining time of the project and within the ability of the test team.

Secondary Objective
The secondary objective of testing application systems will be to: identify and expose all issues and associated risks, communicate all known issues to the project team, and ensure that all issues are addressed in an appropriate matter before release. As an objective, this requires careful and methodical testing of the application to first ensure all areas of the system are scrutinized and, consequently, all issues (bugs) found are dealt with appropriately.

Roles and Responsibilities
Roles and responsibilities may differ based on the actual SOW. Below listed functions are for testing phase.

Developer
An NCI-designated Cancer Center selected and funded by NCICB to participate in a specific Workspace to undertake software or solution development activities. Responsible to:
- Develop the system/application
- Develop Use cases and requirements in collaboration with the Adopters
- Conduct Unit, system, regression and integration testing
- Support user acceptance testing

Adopter
An NCI-designated Cancer Center selected and funded by NCICB to undertake formal adoption, testing, validation, and application of products or solutions developed by Workspace Developers. Responsible to:
- Contribute to Use case, requirement development through review
- Contribute to develop and execution of the development test scripts through review
- Conduct Full User Acceptance, regression, and end-to-end testing; this includes identifying testing scenarios, building the test scripts, executing scripts and reporting test results

Testing Process Management Team
Include NCI, BAH and Cancer Center Leads allocated to the . Group responsible to manage the entire testing process, workflow and quality management with activities and responsibilities to:
- Monitor and manage testing integrity and Support testing activities
- Coordinate activities across cancer centers