Appendix 6 - Test Plan Template.pdf

TEST PLAN TEMPLATE

for the

NATIONAL ARCHIVES AND

RECORDS ADMINISTRATION

Status: Final Date: 05/15/2023 Version: 2.1

<PROJECT TITLE>

TEST PLAN

<Version Number> for the

NATIONAL ARCHIVES AND

RECORDS ADMINISTRATION

<Draft or Final> <Date>

PREPARED BY:

<Testing Organization>

Testing Organization <Project Title>

<DRAFT or FINAL>

Document Change Control Sheet

Document Title: <Project Title>

Date Filename/Version # Author Revision Description

Date Page #Document ID

TABLE OF CONTENTS

DOCUMENT CHANGE CONTROL SHEET 2

1.0 INTRODUCTION 4

1.1 PURPOSE

1.2 PROGRAM OVERVIEW

1.3 ACRONYMS AND DEFINITIONS

1.4 REFERENCED DOCUMENTS

2.0 TEST PROCESS 5

2.1 TEST SCHEDULE OVERVIEW

2.2 ROLES AND RESPONSIBILITIES

2.3 TEST OBJECTIVE

2.3.1 Acceptance Criteria

2.3.2 Defect Management Process

2.3.3 Reviews

2.3.4 Reporting

2.3.5 Test Environment

2.3.6 Test Data

3.0 TEST AND EVALUATION 9

3.1 TEST STRATEGY/TEST TASKS

3.2 TEST COVERAGE

3.2.1 Waivers and Deviations

3.3 ASSUMPTIONS AND CONSTRAINTS

3.4 RISKS AND MITIGATIONS

LIST OF TABLES

Table 1-1: Acronyms List B-5 Table 1-2: Definitions List B-5 Table 2-1: Test Milestones B-6 Table 2-2: Roles and Responsibilities B-7

<Project Title> Test Plan

1.0 INTRODUCTION

This <Project Title> Plan addresses and provides guidance for testing to be performed in support of the National Archives and Records Administration (NARA) < Project Title > program. It is designed to capture and convey the overall interactions and objectives of the <Project Title> Test and Evaluation activities for testing.

1.1 Purpose

This document provides a basis for planning and performing the <Project Title> testing activities. Specifically, this plan documents the following:

• An overview of the test schedule;

• The roles and responsibilities required for successfully completing testing;

• Goals and objectives of the test process;

• An overview of the acceptance criteria (no matter the testing phase or effort the goal is to meet the acceptance criteria);

• An overview of the reporting process;

• A listing of assumptions/constraints and risks/issues and associated with this process;

• Overview of the test strategy, tasks, and coverage;

This Test Plan focuses on the overall test approach used to ensure that the <Project Title> system meets the requirements and needs of the user. Further <Project Title> Test Team duties, activities, and responsibilities will be discussed later in this document.

1.2 Program Overview

<Provide a description of the program/project under test>

1.3 Acronyms and Definitions

<Provide a table with a list of acronyms along with full names that are utilized within this document. The table provided in this section is an example and should be updated according to the project and testing effort being performed>

<Below is an example of the Acronyms List table:>

ACRONYM DESCRIPTION

PMO Program Management Office PMP Program Management Plan PRP Peer Review Process QA Quality Assurance

ACRONYM DESCRIPTION

QC Quality Control QM Quality Management

Table 1-1: Acronyms List

<Provide a table with a list of terms and definitions utilized within this document. The table provided in this section is an example and should be updated according to the project and testing effort being performed.>

<Below is an example of the Definitions List table:>

TERM DEFINITION

Acceptance criteria The criteria that a system or component must satisfy in order to be accepted by a user, customer, or other authorized entity.

Acceptance testing (1) Formal testing conducted to determine whether a system satisfies its acceptance criteria and enables the customer to determine whether to accept the system. (2) Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component.

Defect A document reporting on any event that occurs during the testing process that requires investigation.

Quality Assurance

(QA)

(1) The process of evaluating overall project performance on a regular basis to provide confidence that the project will satisfy the relevant quality standards. (2) The organizational unit that is assigned responsibility for quality assurance. [A Guide to the Project Management Body of Knowledge (PMBOK Guide), 2000 Edition]

Table 1-2: Definitions List

1.4 Referenced Documents

This section lists the industry standards, references, and documents that provide guidance in the development of the <Test Plan>.

2.0 TEST PROCESS

<Provide a very high-level overview of the testing to be performed on <Project Title> as well as any explanation that may be required for the test process >

2.1 Test Schedule Overview

<This section should include a list of key milestones for all test phases covered by this test plan> All test activities are scheduled to be completed before <End Date>. The last activity for testing will be the Test Report covering the test results. A schedule timeline for acceptance testing is presented in Table 2-1 Test Milestones. Reference the project Integrated Schedule for the specific dates.

Below is an example of the Test Milestones table:

Activities Owner Start Date Finish Date Install AAD to ABL Contractor 10/18/11 11/23/11

Conduct Initial Security Scan Contractor 11/15/11 11/30/11 Complete Test Plan NARA 12/20/11 01/13/12

Perform System Testing Contractor 02/01/12 02/14/12 Perform Acceptance Testing NARA 02/15/12 02/20/12

Obtain NARA CCB Approval Contractor /NARA 10/08/11 12/08/11

Cutover to AAD at ABL Contractor 02/21/12 02/22/12 Shutdown AAD at VA Beach Contractor 03/13/12 03/19/12

Test Report NARA 02/21/12 03/01/12

Table 2-1: Test Milestones

2.2 Roles and Responsibilities

<Describe each role and responsibility associated with the testing activities for the <Project Title>. The table provided in this section is an example and should be updated according to the project and testing effort being performed. >

<Below is an example of the Roles and Responsibilities table:>

Roles Required Responsibilities

Test Manager ● Responsible for identifying any formal testing standards, then ensuring that those standards are being followed

● Identifies what to test and determine when testing resources are needed to ensure adequate test preparation

● Monitors and controls test work products and test results

Roles Required Responsibilities

● Oversees overall testing effort

● Reviews and validates test plan

● Reviews test results to determine whether software satisfies project objectives Testing Team ● Supports development of test plan(s)

● Monitors users testing

● Documents and monitors test issues and tracks to closure

● Reviews test results

CM Specialist ● Conducts Configuration Audits

● Manages all CM controlled documentation

Risk Officer ● Track and report risk information to the Program Manager

Development Contractor Support

● Performs system testing

● Supports user testing

● Maintains test environment(s)

● Provides test report

● Develops test scripts and procedures

● Schedules and generates software builds

NARA Subject Matter Expert (SME)

● Executes and validates tests during acceptance testing

● Provides test data

● Provides test results report

Table 2-2: Roles and Responsibilities

2.3 Test Objective

The objective of the test process is to demonstrate that the <Project Title> system is operationally ready for use, to determine the extent to which the <Project Title> has met the requirements, and evaluate the delivered system and products to see if they met the Program Management expectations:

• Ensure the system satisfies user requirements and expectations;

• Identifying discrepancies, deficiencies, and limitations;

• Verify interfaces;

• Demonstrate operational capabilities and prove adequacy of documentation;

• Ensure usability of the system; and

• Ensure the highest quality of the <Project Title> system and code quality.

The goal of system testing (testing performed by the development team) should be the same as above. Even if the next phase is acceptance testing, the system should be verified that it is operationally ready for use.

<If test plan just covers acceptance testing, please see below details; contractors please provide the details on the types of testing that will be done for the project> Before acceptance testing begins the application should have gone through a comprehensive testing effort from the Development Contractor, which includes unit/string, integration, and system testing. Acceptance testing is designed to provide an additional level of confidence and demonstrate that the <Project Title> system is operating as desired.

Verification of system security features/capabilities will be performed by the <Project Title> Security Team. Security testing is not covered in this document.

2.3.1 Acceptance Criteria

<Provide a list of the acceptance criteria that must be met.> The acceptance test criteria require the following actions be completed before testing activities can end:

2.3.2 Defect Management Process

<Provide an overview of the process and tool to be used during the testing activities>

2.3.3 Reviews

<Provide an overview and a high-level agenda of any reviews that will be conducted>

2.3.4 Reporting

<Reporting will be a regular occurrence throughout testing and will be in several different forms: Reviews (if conducted), defect status reporting, Test Result Report, and informal email updates to management.

List each type of reporting to be used during testing and include an overview/outline for those types of reporting >

2.3.5 Test Environment

<Provide a brief description of the test environment and how the environment will be established along with information on the hardware and software needed to execute testing. Provide a list of the test tools needed to support testing that is not part of the software being tested and any software required to record test results>

2.3.6 Test Data

<Describe data to be used during testing in detail. Describe where and how the data will be obtained.>

3.0 TEST AND EVALUATION

The goal of testing is to provide NARA a sufficient level of confidence that the delivered <Project Title> system meets the required objectives. This is accomplished by determining the verification and evaluations that must be covered by the testing activities for this project that will demonstrate that the system is ready for use. This section details the test strategy and the associated tasks to achieve this objective.

3.1 Test Strategy/Test Tasks

<Describe the overall strategy of the testing. Identify the methods and criteria used in performing test activities. Define the specific methods and procedures for each type of test.

Identify the set of tasks necessary to prepare for and perform testing activities. Identify all inter-task dependencies and any specific skills required>

3.2 Test Coverage

<Provide a list of functions (applications, subsystems) that will be verified during the execution of this test plan>

3.2.1 Waivers and Deviations

<If waivers or deviations are required, they must be submitted to NARA management for approval. A deviation for testing is granted for temporary, short-term relief of a requirement or defect whereby future builds/deliveries will be in compliance. A waiver for testing is granted for permanent relief of a requirement or defect.

A requirement associated with an approved deviation will have the status of ‘Pass with Deviation’ in the final test report. All requirements with ‘Pass with Deviation’ will be treated as ‘Passed’ when determining the pass rate. A requirement associated with an approved waiver will have the status of ‘Deferred’ in the final test report and will not be used in determining the pass rate. Provide a list of all waivers and deviations>

3.3 Assumptions and Constraints

<The accomplishment of successful testing will require that certain expectations are met and resources are available. Also the activities that can be achieved are bounded by the project limitations that might be imposed. Provide a list that contains the known assumptions and limitations to performing testing for the <Project Title> system.>

3.4 Risks and Mitigations

<A system will not be devoid of risks and associated mitigations. Similarly, there will be risks that the <Project Title> Testing Team will encounter during testing. Provide a list that contains the currently known risks along with the associated mitigation(s)>