<\/p>\r\n
Software Test Plan – <Sample Project Name><\/p>\r\n
Revision History<\/strong><\/p>\r\n Version Number<\/p>\r\n<\/td>\r\n Release<\/p>\r\n Date<\/p>\r\n<\/td>\r\n Prepared By<\/p>\r\n<\/td>\r\n Reviewed By<\/p>\r\n<\/td>\r\n Approved By<\/p>\r\n<\/td>\r\n Summary of Changes<\/p>\r\n<\/td>\r\n<\/tr>\r\n The purpose of this section is to give a brief description about the project in terms of the domain, technology used and the target audience, etc<\/p>\r\n The purpose of this section is to give a brief description about the various features that will be tested and the features that will not be tested.<\/p>\r\n Following are the types of testing applicable\/not applicable for the project:<\/p>\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 In Scope<\/p>\r\n<\/td>\r\n Out of Scope<\/p>\r\n<\/td>\r\n<\/tr>\r\n<\/thead>\r\n Following are the features to be tested\/not applicable for the project:<\/p>\r\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 In Scope<\/p>\r\n<\/td>\r\n Out of Scope<\/p>\r\n<\/td>\r\n<\/tr>\r\n<\/thead>\r\n The purpose of this section is to describe the approach that will be followed to perform the testing activities<\/p>\r\n The purpose of this section is to give a brief description about the various types of tests that will be performed on the application.<\/p>\r\n The purpose of this section is to validate the test case preparation for all requirements as per the requirement document.<\/p>\r\n The purpose of this section is to describe the process followed for authoring the test cases<\/p>\r\n The purpose of this section is to describe the process followed for executing the test cases<\/p>\r\n The purpose of this section is to describe the pass\/fail criteria.<\/p>\r\n The purpose of this section is to describe the process followed for suspend\/resume testing.<\/p>\r\n The purpose of this section is to describe the process followed to log\/track defects.<\/p>\r\n Following is the SLA for defect management:<\/p>\r\n S. No.<\/strong><\/p>\r\n<\/td>\r\n Severity<\/strong><\/p>\r\n<\/td>\r\n \u00a0Time (Hrs.)<\/strong><\/p>\r\n<\/td>\r\n<\/tr>\r\n<\/thead>\r\n\r\n 1<\/p>\r\n<\/td>\r\n CRITICAL<\/p>\r\n<\/td>\r\n 2<\/p>\r\n<\/td>\r\n HIGH<\/p>\r\n<\/td>\r\n 3<\/p>\r\n<\/td>\r\n MEDIUM<\/p>\r\n<\/td>\r\n The purpose of this section is to give a brief estimation of effort required and the number of resources required and an estimated duration for completing the testing activity.<\/p>\r\n The purpose of this section is to enlist the start date and end date for each phase and the deliverables for the respective phases.<\/p>\r\n S. No.<\/strong><\/p>\r\n<\/td>\r\n Phase<\/strong><\/p>\r\n<\/td>\r\n Tasks<\/strong><\/p>\r\n<\/td>\r\n Start Date<\/strong><\/p>\r\n<\/td>\r\n End Date<\/strong><\/p>\r\n<\/td>\r\n Deliverables<\/strong><\/p>\r\n<\/td>\r\n<\/tr>\r\n<\/thead>\r\n\r\n The purpose of this section is to give a brief description about the hardware\/software requirements needed for performing the testing activities.<\/p>\r\n Tool Name<\/strong><\/p>\r\n<\/td>\r\n Purpose<\/strong><\/p>\r\n<\/td>\r\n<\/tr>\r\n<\/thead>\r\n\r\n The purpose of this section is to describe the training required for Training on the application\/system and any test tools to be used.<\/p>\r\n The purpose of this section is to give a brief description about the roles and responsibilities.<\/p>\r\n The purpose of this section is to list out logical assumptions, identify the prioritized risk and mitigation, contingency plans and identify dependencies (if any).<\/p>\r\n Risks<\/u><\/strong><\/p>\r\n Outline Major Risks in the project.<\/p>\r\n The purpose of this section is to continuously track the competency levels of team\u2019s present knowledge, identify gaps, bridge the gaps and enrich knowledge and skills to become master in the skills required for the project.<\/p>\r\n For any escalations, following are the points of contact during the test process for all test activities.<\/p>\r\n Role<\/strong><\/p>\r\n<\/td>\r\n E-mail<\/strong><\/p>\r\n<\/td>\r\n Mobile<\/strong><\/p>\r\n<\/td>\r\n<\/tr>\r\n<\/thead>\r\n\r\n The purpose of this section is to identify the criteria accepted by the business and ensure quality is met.<\/p>\r\n The purpose of this section is to give a brief description about the effort, schedule and deliverables for automation testing.<\/p>\r\n S. No.<\/strong><\/p>\r\n<\/td>\r\n Phase<\/strong><\/p>\r\n<\/td>\r\n Tasks<\/strong><\/p>\r\n<\/td>\r\n Start Date<\/strong><\/p>\r\n<\/td>\r\n End Date<\/strong><\/p>\r\n<\/td>\r\n Deliverables<\/strong><\/p>\r\n<\/td>\r\n<\/tr>\r\n<\/thead>\r\n\r\n The purpose of this section is to give a brief description about the effort, schedule and deliverables for performance testing.<\/p>\r\n S. No.<\/strong><\/p>\r\n<\/td>\r\n Phase<\/strong><\/p>\r\n<\/td>\r\n Tasks<\/strong><\/p>\r\n<\/td>\r\n Start Date<\/strong><\/p>\r\n<\/td>\r\n End Date<\/strong><\/p>\r\n<\/td>\r\n Deliverables<\/strong><\/p>\r\n<\/td>\r\n<\/tr>\r\n<\/thead>\r\n\r\n The purpose of this section is to enlist modes to be used to update the status to the client.<\/p>\r\n Include information about metrics that will be used to showcase<\/p>\r\n\n Software Test Plan – <Sample Project Name> Revision History Version Number Release Date Prepared By Reviewed By Approved By Summary of Changes \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Introduction Purpose The purpose of this section is to give a brief description about the project in terms of the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1860","post","type-post","status-publish","format-standard","hentry","category-automation","has-post-title","has-post-date","has-post-category","has-post-tag","has-post-comment","has-post-author",""],"_links":{"self":[{"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/posts\/1860","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/comments?post=1860"}],"version-history":[{"count":4,"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/posts\/1860\/revisions"}],"predecessor-version":[{"id":19620,"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/posts\/1860\/revisions\/19620"}],"wp:attachment":[{"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/media?parent=1860"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/categories?post=1860"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.testingdocs.com\/questions\/wp-json\/wp\/v2\/tags?post=1860"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\r\n\r\n
\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n Introduction<\/h1>\r\n
Purpose<\/h2>\r\n
Scope of Testing<\/h2>\r\n
\r\n
Testing Types<\/h3>\r\n
\r\n\r\n
\r\n \r\n\r\n \r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n Features<\/h3>\r\n
\r\n\r\n
\r\n \r\n\r\n \r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n Test Approach<\/h2>\r\n
\r\n
\u00a0Types of Tests to be conducted<\/h3>\r\n
Requirements Traceability Matrix<\/h3>\r\n
Test Case Preparation Approach<\/h3>\r\n
\u00a0Test Execution Process<\/h3>\r\n
Pass \/ Fail Criteria<\/h4>\r\n
Suspension and Resumption Criteria<\/h4>\r\n
Defect Management<\/h3>\r\n
\r\n\r\n
\r\n \r\n \r\n \r\n \r\n \r\n \r\n \u00a0<\/td>\r\n<\/tr>\r\n \r\n \r\n \r\n \u00a0<\/td>\r\n<\/tr>\r\n \r\n \r\n \r\n \u00a0<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n Test Effort and Schedule<\/h2>\r\n
\u00a0Test Effort<\/h3>\r\n
Test Schedule<\/h3>\r\n
\r\n\r\n
\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n Test Environment<\/h2>\r\n
Hardware Environment<\/h3>\r\n
Software Environment<\/h3>\r\n
Test Tools<\/h3>\r\n
\r\n\r\n
\r\n \r\n \r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n Staffing and Training Needs<\/h2>\r\n
Roles and Responsibilities (RACI)<\/h2>\r\n
Risks, Issues and Dependencies<\/h2>\r\n
Skill Gap Analysis<\/h2>\r\n
Escalation Approach<\/h2>\r\n
\r\n\r\n
\r\n \r\n \r\n \r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n Acceptance and Sign-off Criteria<\/h2>\r\n
Automation Testing<\/h2>\r\n
\r\n\r\n
\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n Performance Testing<\/h2>\r\n
\r\n\r\n
\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n \r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n \u00a0<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n \u00a0Test Status Reporting<\/h2>\r\n
\u00a0Test Metrics<\/h2>\r\n