Scribd
Upload
46 views

Project Testing Plan - Guidelines: Purpose

The document provides guidelines for a project testing plan, including its purpose to communicate the overall testing process and results to stakeholders. It outlines who participates in testing, what will be tested, when and where testing occurs, and how testing will be conducted. It also describes different types of testing like unit, function, integration, verification, performance, system, and user acceptance testing. Templates are provided for an overall testing plan and individual testing type guides.

Uploaded by

pmpcville
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
46 views

Project Testing Plan - Guidelines: Purpose

The document provides guidelines for a project testing plan, including its purpose to communicate the overall testing process and results to stakeholders. It outlines who participates in testing, what will be tested, when and where testing occurs, and how testing will be conducted. It also describes different types of testing like unit, function, integration, verification, performance, system, and user acceptance testing. Templates are provided for an overall testing plan and individual testing type guides.

Uploaded by

pmpcville
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Project Testing Plan - Guidelines

Purpose:

The primary purpose of a Project Test Plan is to communicate the overall testing process and results to
all of the appropriate project stakeholders: project team, business owners, sponsor and management.

It provides a roadmap to:

• Who participates
• What is to be tested
• When and where testing will take place
• How testing will be conducted and recorded.

Testing is a form of validation and verification activities.

A. Validation demonstrates that the product, as provided, will fulfill its intended use.

Validation activities use approaches similar to verification (e.g., test, analysis, inspection, demonstration,
or simulation). Often, the end-users and other relevant stakeholders are involved. Both validation and
verification activities can run concurrently and may use portions of the same environment.

o Validation answers the question: “Are we building the product right?”

B. Verification addresses whether the work product properly reflects the specified requirements.

Verification is inherently an incremental process because it occurs throughout the development of the
product and should be applied to all work products. The Verification process involves the following:
preparation, performance, and identification of corrective action. Verification of work products
substantially increases the likelihood that the product will meet the customer, product, and product-
component requirements. Peer reviews are an important part of verification and are a proven
mechanism for effective defect removal.

o Verification answers the question: “Are we building the right product?”

1
Testing Types:

There are many different test types. Identification of who should perform each test type is noted below.
Other test activities can occur above-and-beyond the core types listed.

Unit Test - Confirms that the program logic within an application module produces the expected output
when given a known input. Written from a developer’s perspective, this ensures that the smallest
testable module of an application successfully performs a specific task(s). Unit tests tell a developer that
the code is working properly

Function Test - Confirms that the logically-grouped modules function according to specifications.
Developers write this test from a user’s perspective. Testing is based on output only, without any
knowledge of internal code or logic. Function tests tell a developer that the code is working properly.

Integration Test – Verifies that a product or product component fulfills its intended use when placed in
its intended environment. Any testing stakeholder can conduct this test.

Verification Test - Verifies that a product or product component fulfills its intended use when placed in
its intended environment. Any testing stakeholder can conduct this test

Performance Test - Measures software performance of batch data, under actual or anticipated volume,
as well as on-line transaction response times. Executed by the technical team, this test verifies
performance requirements, throughput, and growth capacity. Performance tuning continues
throughout the system lifecycle.

System Test - Verifies that functional business requirements, business processes, data flows, and other
system criteria are met. The technical team tests specific end-to-end business processes until the
complete application environment mimics real world use.

User Acceptance Test (UAT) - Validates that the system, as a whole, meets mutually agreed-upon
requirements. UAT is completed by end-users of the application and occurs before a client or customer
accepts the new system.

Testing Plan Template

2
Resource for Individual Testing Types:

Unit Test <Guide Link Here>

Function Test <Guide Link Here>

Integration Test <Guide Link Here>

Verification test <Guide Link Here>

Performance test <Guide Link Here>

System Test <Guide Link Here>

User Acceptance Test <Guide Link Here>

You might also like