{Name} System
[Version|Release m.n]
− instructions to be deleted once they have been followed, e.g., select one of
the following alternatives.
• The vertical bar within braces or brackets specifies a choice: either this|or that.
To prepare the plan, fill in the information specified within the Template, as described
above, guided by the UAT methodology. Change the footer to reflect the plan being
produced, with its version and date. The Test Plan Sample provides an example of a
test plan following the template. The text may also be varied as required, as long as
the underlying approach is followed.
Familiarity with Word 6.0 is assumed. The following are some key tips:
• If not familiar with using styles, to get a heading of any level, copy an existing one
and insert it where the new heading is needed. The number will be updated
automatically. Then change the text as needed.
• Update the Table of Contents at any time by placing the cursor in it and hitting F9.
The entire Table of Contents should be updated, not just the page numbers, if you
have added or changed headings at Level 1 or 2.
• These instructions are placed within the Template for convenience of reference.
Delete this entire page when finished, and do a final update of the Table of
Contents.
The business purpose of the {name} System is {brief statement of overall business
functionality}.
• {list/describe briefly}.
[The attachments contain the following parts of the plan that are lengthy and/or are
prepared by software other than word processing:] {Select/change the items in the
following list as needed. Note if item is stored separately rather than as part of this
document.}
{Describe involvement in test planning, test case development and/or test execution,
including reviews and signoffs}
1.
2.
1.3. Assumptions
Prior to acceptance testing, the tests listed below will have been performed, and the
results reviewed by the User Acceptance Testing group. These tests are considered to
have been satisfactorily completed, with the exceptions noted below.
This test plan describes all of the remaining tests to be performed on the {system|
release} [except for describe any subsequent tests not covered by this plan and
reference the appropriate test plan(s)].
The software and non-software deliverables will be made available to the UAT group in
builds, as detailed in the Build Strategy Section below.
The entire system will be made available to the UAT group at one time on or before the
above start date. Hence the term “build” as used in this plan refers only to the top level
of the test hierarchy structure.
Adequate staff resources with appropriate knowledge and/or training will be available
as specified in the work plan during the period required to set up and complete the test.
Risks that may impact the ability to complete the acceptance test successfully and on
time:
Risks that may impact the ability to install the system on time and/or operate the system
successfully:
2. Parallel testing against {release m.n of this system|the {name} system|the {name}
process} in the {UAT|production} environment at {location}.
• Environment tests: Tests that validate the functioning of the system with the
hardware, system software and networks.
• Positive functional tests: Response to valid user actions and valid data.
• Negative functional tests: Response to user actions or data that should generate
error messages.
• Invalid input tests: Response to inputs or user actions that may be unanticipated by
the system design.
• Usability tests: Verification of the ease of use of the system and its associated
documentation and procedures, including recovery procedures.
• Control tests: Tests of the system’s ability to produce appropriate audit trails.
• Regression tests: Repeated tests in any of the above categories that verify that
problems were fixed, or other changes were made, correctly and without adverse
impact on other functions.
The requirements to be validated by this test plan have been identified and
decomposed hierarchically, and are shown {below|in Attachment A}.
This acceptance test of a new system is designed to validate nnn% {normally 100%} of
the requirements relating to the environment, the software deliverables, and the non-
software deliverables. {Describe any exceptions.}
{Other approach.}
The sequence of builds reflects the following dependencies and other factors relating
to the development and/or testing processes and the functionality to be delivered:
Builds will be moved to pilot testing {individually|all at one time}. {Detail as required}.
{Reproduce either of the subsections below for each build. Build numbers should be
unique through all builds.}
2.5.1.1.Description
2.5.1.2.Test Runs
The tests for this build will be divided into the following test runs, each generally
representing a single on-line session or batch job unless otherwise described in the
text:
2.5.1.3.Test Files
The following test files must be available to test this build: The names provide a
reference to the Test Execution section below.
{*e.g., empty file, valid records, records processed by specified subsystem or function}
2.5.1.4.Test Tools
2.5.2.1.Description
• {Name: description}
2.5.2.2.Acceptance Criteria
2.5.2.3.Validation Method(s)
• {List approach(es), e.g., inspection, review, user test. If appropriate, list test runs as
above.}
{Repeat the following as required for each build, including any non-software builds that
will be validated by actual testing.}
The following matrices have been used in determining the test case strategy and
verifying coverage of detail-level requirements by test cases. An “X” under a test case
number indicates that the test case tests the requirement at the left.
3.4.1.Hardware
Issues: {Describe any potential conflicts or other issues impacting software availability,
their impact, and how they will be dealt with, or indicate “None.”}
3.4.3.Networks
{For each of the following, reference may be made to existing documented procedures,
giving version and date, and describing any exceptions for this project. Otherwise
describe procedures in detail. Suggested text is included below.}
The Problem Reporting procedure found in Section 2.07 of the UAT Life Cycle Version
2.0 will be used to document and control problem reports and change requests during
normal acceptance test execution. Testers will document all problem reports and
change requests using the system TR form. This facility can be accessed directly from
the test scripts in Notes.
Before the initial pilot rollout, the Certification procedure specified in Section 2.09 of the
UAT Methodology will be followed.
Each of the test runs defined above consists of one or more test cases {as listed below|
as listed in Attachment D}.
The listing of test cases has been developed as the {name of report} produced by {tool
or environment} on {workstation/server identification} from the input file {drive:\directory
path\file}. [A hard copy listing is found in Attachment D.] {Hard copy should be
attached unless access to the on-line material is available and familiar to all
concerned.}
Coverage of detail-level requirements by the test cases listed for each build is validated
by the Detail-Level Validation Matrices or equivalent (see Section 2.8).
The details of each test case, and associated test scripts, are stored in the {Name}
Lotus Notes database.
6.1.1.Software Components
The following new or changed (N/C) software components will be tested. {Include all
types of components, including JCL, DBMS coding, etc.}
6.1.3.User Documentation
The following existing, new or changed (E/N/C) user procedures or other
documentation will be referenced and applied during test execution. New or changed
procedures or other documentation (non-software deliverables) will be tested as part of
the acceptance test:
{*May be left blank if the same procedures are used in all builds.}
{*May be left blank if the same procedures are used in all builds.}
{*May be left blank if the same components are used in all builds.}
{**E.g., flat file, VSAM file, database, database table - specify DBMS name where
applicable.}
{***Indicate if access by the build is Create, Read, Update or Delete (C/R/U/D) as well
as any access by other systems or builds.}