Use this template when designing a complex software project. The STP worksheet will help you develop a comprehensive testing plan to ensure the project conforms to your clients specifications and contractual obligations.
The Project Management Pack suite of templates compliments the proposal and contract documents by giving you a collection of business documents to be used once you have a project to work on.
Alternate and related documents are also listed if there are other templates similar in nature, on a different scale or which can be used to provide additional information.
A wide variety of documents are included and are intended to be picked based on your needs. All projects are different and have different needs and goals. Pick the collection of documents from our collection and use them as needed for your project. Recommendations and samples provided are only intended as general guidelines.
Project documents may also be referred to as a template, document, outline, boilerplate, letter, sample, form or example.
Additional search terms related to this document:
business, project, management, information, documents, templates, boilerplate, form, outline, text Software Testing Plan STP STP TITLE Author Title Company CurrentDate Document Version Control Information Introduction Purpose this document Objectives Insert the purpose this document its objectives and its intended audience. Scope document Insert description the scope this Software Testing Plan Scope Constraints Insert constraints such schedules costs interactions overview any other information relevant the testing the development requirements. Overview Insert overview brief description the product software other desired end result that being tested under this Software Testing Plan. Business Context Insert overview the business organization desiring the development this project Include the business organization mission statement and its organizational goals and objectives Note you have already completed Software Requirements Specification the majority this material copied verbatim from that document The purpose this preamble familiarize staff recently attached the testing portion project who may not have been present involved with earlier stages the project. Testing Strategy Insert general overview the strategy and plan for meeting the testing deliverables Describe the levels testing that will need take place and the type testing activities more detailed outline will provided further this document there are specific tests that need follow their own STP you can describe them additional document separate from this main document. Testing Strategy Outline will include The individual items tested The purpose for testing those items The individual features tested The individual features NOT tested The managerial and technical approach testing The criteria for pass failure testing The individual roles responsibilities participants testing The milestones and deliverables required for testing The schedules and timelines for individual tests the Software Testing Plan whole. The risk assumptions and constraints placed upon the Software Testing Plan. References Reference Material Insert list all reference documents and other materials related the Software Testing Plan References will often include but are not limited. Software Requirements Specifications Software Development Plan Software Quality Assurance Plan Software Management Plan Project Outline and Management Plan Documentation Items Insert references documentation including but not limited Software Requirements Specification SRS Software Design Specification SDS Software Development Plan SDP Software Installation Guide Software Users Guide Software Features Guide Software Bug Error Correction Defect Removal Guide Items Tested Program Modules Insert description the testing performed for each module that the software contains. Job Control Procedures Insert description the procedures followed for testing the job control language JCL including scheduling for production control and all job sequencing This section should include all the relationships between the above mentioned items the Program Modules section. User Procedures Insert description the testing conducted user documentation and support resources online printed ensure that they are complete and comprehensive. Operator Procedures Insert description the testing procedures conducted ensure that the software can run and supported within production environment intended and that any Help Desk other support services outlined the plan can verified effective and meeting the intended support outcomes outlined the goal the Software Testing Plan. Features Tested Insert the objectives and requirements for features that are being tested this Software Testing Plan. Features Not Tested Insert the objectives and requirements for features that are NOT being tested this Software Testing Plan. Approach Insert the objectives and requirements for the overall approach testing The approach should cover such major tasks the identification time estimates for each element the Software Testing Plan Identify the different types testing and describe their testing methods and the criteria for evaluating such testing Your Software Testing Plan may contain several different approaches for certain elements. Component Testing Insert the objectives and requirements verify the implementation integrity and functionality for single unit component module group individual software elements components Component Testing performed verify that the individual component group components complete and functioning intended. Integration Testing Insert the objectives and requirements verify the implementation integrity and functionality for combined units such individual software units components group individual software elements components that has been combined with hardware elements Integration testing important ensure that the software functional whole within the environment intended run The Integration Testing performed ensure that all operational requirements are met. Conversion Testing Insert the objectives and requirements for testing that all historical data elements convert are compatible with the new system Conversion testing required only the software upgrade older system will use manipulate data from other systems. Job Stream Testing Insert the objectives and requirements for testing that the software operates correctly the production environment. Interface Testing Insert the objectives and requirements for testing that the software operates correctly with all user interface and input systems. Recovery Testing Insert the objectives and requirements for testing that the software recovery and restore operations function correctly and all backup systems and procedures work intended the production environment. Performance Testing Insert the objectives and requirements for testing that the software operates correctly regards normal operation response and execution times scalability portability and all other performance requirements within the production environment. Regression Testing Insert the objectives and requirements for testing that any changes applied the software not affect functions previously tested. Acceptance Testing Insert the objectives and requirements for testing that the software system meets all criteria and deliverables The Acceptance Testing important ensure that all requirements are met and that all components modules hardware requirements and recovery and restore operations function the production environment and that plan exists demonstrate such functionality for customer client. Alpha Beta and Release Candidate Testing Insert the objectives and requirements for testing that will done customer client verify that the software meets all deliverables and requirements from the Software Requirements Specifications SRS the Software Development Plan SDP and detect any errors bugs defects the software. Pass and Failure Criteria This section describes the criteria determine whether specific item has passed failed particular test. Criteria for Suspension This section will describe the criteria for suspending individual element group elements for particular testing activity. Criteria for Resumption Testing This section will describe the criteria for resuming testing for individual element group elements that has been previously suspended. Criteria for Approval Testing This section will describe the criteria for acceptance and approval for individual element group elements. Testing Process and Methods Insert the specific testing process and methods used performing each testing activity this section you will describe and define each type test that the Software Testing Plan contains You may attach additional exhibits this section your testing plan requires them. Test Deliverables Insert the specific deliverables and documents that are delivered from the testing process Test deliverables may include incremental data data derived from incomplete tests Typical test deliverables include but are not limited. Individual Test Element Module Summary Reports Group Element Module Summary Reports Individual and Combined Test Logs Test Metrics and Benchmark Reports Test Input and Output Reports Test Incident Reports Testing Task Requirements List description tasks and the skills required for performing testing part the deliverables. Examples Task Name Insert description here Responsibility for Task Insert description here Resources Required for Task Insert description here Schedule Timeline for Task Insert description here Testing Hardware Environmental Requirements List description the hardware and environmental requirements for performing testing part the deliverables. Examples Hardware Requirement Name Insert description here Software Requirement Name Insert description here Security Resources Requirement Name Insert description here Specific Tools Requirement Name Insert description here Specific Documentation Requirement Name Insert description here Specific Risks and Assumptions Insert description here Focus restraints such resource availability time constraints staff and developer availability and all other external factors that can influence testing. Risk and Assumption Contingency Plan Insert description the contingency plan for each item listed above Change Request and Management description the Software Testing Plan change request and change management procedure Describe the process that must followed for submission review and authorization for all requests for change the Software Testing Plan any change any part the deliverables. Approval for Software Testing Plan description the personnel authorized approve the Software Testing Plan Their Name Title and signature must accompany this document. Approver Title Date signed Approver Title Date signed Approver Title Date signed Approver Title Date signed Appendices description all other supporting information required for the understanding and execution the Software Testing plan and requirements. All Software Testing Plan documents require the following two appendices Definitions Acronyms Abbreviations description the definition important terms abbreviations and acronyms This may also include Glossary terms. References listing all citations all documents and meetings referenced used the preparation this Software Testing Plan and testing requirements document. Customer Initials Developer Initials
Software Testing Plan
