Department Of Health And Human Services Checklist Test Plan

ADVERTISEMENT

D
H
H
S
EPARTMENT OF
EALTH AND
UMAN
ERVICES
<OPDIV Logo>
E
P
L
C
F
NTERPRISE
ERFORMANCE
IFE
YCLE
RAMEWORK
C
C
C
H
E
C
K
L
I
S
T
H
E
C
K
L
I
S
T
H
E
C
K
L
I
S
T
T
P
EST
LAN
Issue Date: <dd/mm/yyyy>
Revision Date: <dd/mm/yyyy>
Document Purpose
The purpose of this document is to provide a quick checklist for use by the project manager to ensure that
all appropriate activities related to the Test Plan have been addressed.
High Level Test Objectives
To ensure that the [work product] satisfies all project requirements.
To ensure that all components of the [work product] function according to design.
To ensure that all use case scenarios can be executed successfully.
To ensure that the [work product] can perform under the anticipated user load.
To determine if the application is intuitive and easy to use, and if it presents the users with the
intended user experience.
Testing schedule/Resources/Status
Milestone/Test phase
Duration (days)
Resources
Date(s)
Status
Unit testing
Functional testing
Load testing
Volume testing
Acceptance testing
Usability testing
Compatibility Testing
Conformance
Testing
Regression Testing
Stress Testing
Vulnerability Testing
Activities Checklist
This section provides a checklist that may be used during the preparation, implementation, and review of
testing activities depending on the types of testing conducted.
Checklist
Have you set up the following for each type of testing:
Environment
URL
Access Instructions
User ID/password
Unit Testing
Unit tests are basic tests at the module level to ensure that a given function works. Unit testing is
generally performed by the programmer or developer while building a system.
Has the test data required for the particular test been identified?
Does the unit testing validate the data at the field level?
Have any preconditions been setup?
Have step-by-step test instructions (including sample input data) been set up?
Has the process for how original data will be recovered before and after test execution been
described?
Has how test data will be identified, maintained, and version-controlled been described?
Test Plan<OPDIV> Test Plan Checklist (v1.0)
Page 1 of 5
This document is 508 Compliant
[Insert additional appropriate disclaimer(s)]

ADVERTISEMENT

00 votes

Related Articles

Related forms

Related Categories

Parent category: Business
Go
Page of 5