usually prepared by the Test Lead or Test Manager and the focus of the document is to describe what to test, what not to test, how work history resume format to test when to test and who will do what test. 11.7 Test Deliverables Describe the deliverables that will result from the testing process (documents, reports, charts, etc.). Also identify groups responsible for providing the test environment. Performance, covers performance testing of a software / phase. Also, include a description of those items agreed not to be tested. How To Prepare Effective Test Plan? Test Plan Objectives. There is no need to test this feature. 4.7 Test Deliverables Describe the deliverables that will result from the testing process (documents, reports, charts, etc.). Features TO BE tested Identify all software features and combinations of software features that will be tested. Note: Provide reasoning for exclusion, like, non-impacted / less impacted / less priority features, as applicable. 3.2 Items to be Tested / Not Tested Describe the items/features/functions to be tested that are within the scope of this test plan. In this post, we will learn how to write a Software Test Plan Template. Test plans can be of different levels and types, depending upon the scope of testing. Participants, who will be conducting Stress Testing on your project? 8.5 Test Pass / Fail Criteria Describe the criteria used to determine if a test item has passed or failed its test. List the individuals whose signatures are required. . Signature: Date: Print Name: Title: Role: Signature: Date: Print Name: Title: Role: Signature: Date: Print Name: Title: Role: Insert the name, version number, description, and physical location of any documents referenced in this document. . Provide space for the signatures and dates.