Software Test Plan (STP)
Template
Software Test Plan
1. INTRODUCTION
The Introduction section of the Software Test Plan (STP) provides an overview of the project and the product test strategy, a list of testing deliverables, the plan for development and evolution of the STP, reference material, and agency definitions and acronyms used in the STP.
The Software Test Plan (STP) is designed to prescribe the scope, approach, resources, and schedule of all testing activities. The plan must identify the items to be tested, the features to be tested, the types of testing to be performed, the personnel responsible for testing, the resources and schedule required to complete testing, and the risks associated with the plan.
1.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.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
9/22/2018
9:27:27 AM
Software Test Plan
1.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.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.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: ? ? ? ? ? ? ? ?
9/22/2018
9:27:27 AM
2
Requirements specification, Design specification, Users guide,
Operations guide, Installation guide,
Features (availability, response time), Defect removal procedures, and Verification and validation plans.)
Software Test Plan
2.1 Program Modules
(Outline testing to be performed by the developer for each module being built.)
2.2 Job Control Procedures
(Describe testing to be performed on job control language (JCL), production scheduling and control, calls, and job sequencing.)
2.3 User Procedures
(Describe the testing to be performed on all user documentation to ensure that it is correct, complete, and comprehensive.)
(Describe the testing procedures to ensure that the application can be run and supported in a production environment (include Help Desk procedures)).
2.4 Operator Procedures
3. FEATURES TO BE TESTED
(Identify all software features and combinations of software features to be tested. Identify the test design specifications associated with each feature and each combination of features.)
4. FEATURES NOT TO BE TESTED
(Identify all features and specific combinations of features that will not be tested along with the reasons.)
9/22/2018
9:27:27 AM
3
Software Test Plan
5. APPROACH
(Describe the overall approaches to testing. The approach should be described in sufficient detail to permit identification of the major testing tasks and estimation of the time required to do each task. Identify the types of testing to be performed along with the methods and criteria to be used in performing test activities. Describe the specific methods and procedures for each type of testing. Define the detailed criteria for evaluating the test results.)
(For each level of testing there should be a test plan and the appropriate set of deliverables. Identify the inputs required for each type of test. Specify the source of the input. Also, identify the outputs from each type of testing and specify the purpose and format for each test output. Specify the minimum degree of comprehensiveness desired. Identify the techniques that will be used to judge the comprehensiveness of the testing effort. Specify any additional
completion criteria (e.g., error frequency). The techniques to be used to trace requirements should also be specified.)
5.1 Component Testing
(Testing conducted to verify the implementation of the design for one software element (e.g., unit, module) or a collection of software elements. Sometimes called unit testing. The purpose of component testing is to ensure that the program logic is complete and correct and ensuring that the component works as designed.)
5.2 Integration Testing
(Testing conducted in which software elements, hardware elements, or both are combined and tested until the entire system has been integrated. The purpose of integration testing is to ensure that design objectives are met and ensures that the software, as a complete entity, complies with operational requirements. Integration testing is also called System Testing.)
5.3 Conversion Testing
(Testing to ensure that all data elements and historical data is converted from an old system format to the new system format.)
5.4 Job Stream Testing
(Testing to ensure that the application operates in the production environment.)
9/22/2018
9:27:27 AM
4
软件测试计划模板-英文版
