{"id":880,"date":"2023-09-09T08:17:52","date_gmt":"2023-09-09T08:17:52","guid":{"rendered":"https:\/\/www.softwaretestingstuff.com\/?p=880"},"modified":"2023-09-10T10:37:59","modified_gmt":"2023-09-10T10:37:59","slug":"testing-bible-software-test-plan","status":"publish","type":"post","link":"https:\/\/www.softwaretestingstuff.com\/2008\/11\/testing-bible-software-test-plan.html","title":{"rendered":"Testing Bible – Software Test Plan"},"content":{"rendered":"\n
A test plan is a document describing the approach to be taken for intended testing activities and serves as a service level agreement between the quality assurance testing function and other interested parties, such as development. A test plan should be developed early in the development cycle and help improve the interactions of the analysis, design, and coding activities. A test plan defines the test objectives, scope, strategy and approach, test procedures, test environment, test completion criteria, test cases, items to be tested, the tests to be performed, the test schedules, personnel requirements, reporting procedures, assumptions, risks, and contingency planning.<\/p>\n\n\n\n