Software Test Plan

Template

Software Quality Assurance Plan

$1.$ INTRODUCTION

$1\mathrm{.}1$ Objectives

$($Describe$,$ at a high level, the scope, approach, resources, and schedule of the testing activities. Provide a concise summary of the test plan objectives, the products to be delivered, major work activities, major work products, major milestones, required resources, and master high$-$level schedules, budget, and effort requirements.$)$

$1\mathrm{.}2$ Testing Strategy

Testing is the process of analyzing a software item to detect the differences between existing and required conditions and to evaluate the features of the software item. $($This may appear as a specific document $($such as a Test Specification$),$ or it may be part of the organization's standard test approach. For each level of testing, there should be a test plan and an appropriate set of deliverables. The test strategy should be clearly defined and the Software Test Plan acts as the high$-$level test plan. Specific testing activities will have their own test plan. Refer to section $5$ of this document for a detailed list of specific test plans.$)$

Specific test plan components include:

$$ Purpose for this level of test,

$$ Items to be tested,

$$ Features to be tested,

$$ Features not to be tested,

$$ Management and technical approach,

$$ Pass $/$ Fail criteria,

$$ Individual roles and responsibilities,

$$ Milestones,

$$ Schedules, and

$$ Risk assumptions and constraints.

$1\mathrm{.}3$ Scope

$($Specify the plans for producing both scheduled and unscheduled updates to the Software Test Plan $($change management$).$ Methods for distribution of updates shall be specified along with version control and configuration management requirements must be defined.$)$

Testing will be performed at several points in the life cycle as the product is constructed. Testing is a very 'dependent' activity. As a result, test planning is a continuing activity performed throughout the system development life cycle. Test plans must be developed for each level of product testing.

$1\mathrm{.}4$ Reference Material

$($Provide a complete list of all documents and other sources referenced in the Software Test Plan. Reference to the following documents $($when they exist$)$ is required for the high$-$level test plan:

$$ Project authorization,

$$ Project plan,

$$ Quality assurance plan,

$$ Configuration management plan,

$$ Organization policies and procedures, and

$$ Relevant standards.$)$

$1\mathrm{.}5$ Definitions and Acronyms

$($Specify definitions of all terms and agency acronyms required to properly interpret the Software Test Plan. Reference may be made to the Glossary of Terms on the IRMC web page.$)$

$2.$ TEST ITEMS

$($Specify the test items included in the plan. Supply references to the following item documentation:

$$ Requirements specification,

$$ Design specification,

$$ Users guide,

$$ Operations guide,

$$ Installation guide,

$$ Features $($availability$,$ response time$),$

$$ Defect removal procedures, and

$$ Verification and validation plans.$)$

$2\mathrm{.}1$ Program Modules

$($Outline testing to be performed by the developer for each module being built.$)$

$2\mathrm{.}2$ Job Control Procedures

$2\mathrm{.}3$ User Procedures

$2\mathrm{.}4$ Operator Procedures

$3.$ FEATURES TO BE TESTED

$4.$ FEATURES NOT TO BE TESTED

$5.$ APPROACH

$5\mathrm{.}1$ Component Testing

$5\mathrm{.}2$ Integration Testing

$5\mathrm{.}3$ Conversion Testing

$5\mathrm{.}4$ Job Stream Testing

$5\mathrm{.}5$ Interface Testing

$5\mathrm{.}6$ Security Testing

$5\mathrm{.}7$ Recovery Testing

$5\mathrm{.}8$ Performance Testing

$5\mathrm{.}9$ Regression Testing

$5\mathrm{.}10$ Acceptance Testing

$5\mathrm{.}11$ Beta Testing

$6.$ PASS $/$ FAIL CRITERIA

$6\mathrm{.}1$ Suspension Criteria

$6\mathrm{.}2$ Resumption Criteria

$6\mathrm{.}3$ Approval Criteria

$7.$ TESTING PROCESS

$7\mathrm{.}1$ Test Deliverables

$7\mathrm{.}2$ Testing Tasks

$7\mathrm{.}3$ Responsibilities

$7\mathrm{.}4$ Resources

$7\mathrm{.}5$ Schedule

$8.$ ENVIRONMENTAL REQUIREMENTS

$8\mathrm{.}1$ Hardware

$8\mathrm{.}2$ Software

$8\mathrm{.}3$ Security

$8\mathrm{.}4$ Tools

$8\mathrm{.}5$ Publications

$8\mathrm{.}6$ Risks and Assumptions

$9.$ CHANGE MANAGEMENT PROCEDURES

$10.$ PLAN APPROVALS