A test plan is a systematic approach for testing a software application that contains detailed testing information including the scope of testing, scheduling, deliverables, release criteria, risks, and contingencies. The test plan template includes sections for test plan identification, references, introduction, features to be tested and not tested, entry and exit criteria, deliverables, responsibilities, risk mitigation strategies, approvals, and a glossary.
A test plan is a systematic approach for testing a software application that contains detailed testing information including the scope of testing, scheduling, deliverables, release criteria, risks, and contingencies. The test plan template includes sections for test plan identification, references, introduction, features to be tested and not tested, entry and exit criteria, deliverables, responsibilities, risk mitigation strategies, approvals, and a glossary.
A test plan is a systematic approach for testing a software application that contains detailed testing information including the scope of testing, scheduling, deliverables, release criteria, risks, and contingencies. The test plan template includes sections for test plan identification, references, introduction, features to be tested and not tested, entry and exit criteria, deliverables, responsibilities, risk mitigation strategies, approvals, and a glossary.
A test plan is a systematic approach for testing a software application that contains detailed testing information including the scope of testing, scheduling, deliverables, release criteria, risks, and contingencies. The test plan template includes sections for test plan identification, references, introduction, features to be tested and not tested, entry and exit criteria, deliverables, responsibilities, risk mitigation strategies, approvals, and a glossary.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 2
Test Plan
It is a systemic approach for testing a software application. The test plan
typically contains a detailed understanding of how the workflow will be. In software testing, a Test Plan contains detailed testing information regarding upcoming testing efforts which include the scope of testing, scheduling, test deliverables, release criteria, risk, and contingencies.
Test Plan template contains the following information
Test Plan Identifier is used in configuration management and used for
versioning of Test plan.
References contain all the referred document such as project plan
software requirement specification and detailed design document etc.
The introduction defines the purpose of defining the Test Plan which covers scope and objective of Test Plan.
Software risk issue covers all the possible risk which may arise due to complexity or misunderstanding of various application related requirements. There may also be other reasons causing risk.
Features to be tested includes all the features that require being tested in the application.
Features not to be tested include all the features that require not to be tested. There are many reasons for mentioning the items which won’t be part of the testing process. Some of the reasons are, these items or modules were already tested earlier and is currently stable or it is to be tested in next cycle. Even very low risk, trivial or rarely used functionalities are left out so that testers can focus and emphasize on the major ones.
Entry and exit criteria define when to start testing and when to stop testing. Suspension criteria and resumption criteria define when to suspend testing and when to resume testing. This is done to mark the duration when the application is not fit for testing and is sent back to the development team to release a stable build for testing.
Test deliverables are the documents prepared during the testing
process and are shared with stakeholders. Responsibilities include who will be responsible for which testing process.
Risk mitigation and contingency strategies lay down the guidelines for all the possible risks that the testing team might encounter and the different ways to handle them, once they arise.
Approvals need to be taken for the testing process, the various testing related documents and for the various deliverables. The glossary includes terms and terminology to be used during the testing process.
