Test Plan is created and maintained by the test lead/ QA lead. Only the QA lead should be able edit in a controlled manner. Inputs are got from Functional Requirement Document(FRD) to create the Test Plan. It is impossible to add, review, document, update, and maintain the Test Plan on his/her own. So developers plays a supporting role or contributing role but they are not responsible for maintaining the Test Plan.
Test Plan creation start at the define/analysis phase of the SDLC.
Test Plan Includes,
Inputs – Project Dates , No Of People, FRD (Functional Requirement Document – Scope Of Testing)
Actors – QA Lead, Team members going to participate or provide their inputs
Outputs – Test Plan Document (TPD)
What is?
When? – 1st Step Of STLC
How?
Table of Contents of a Test Plan –
[Managerial Parts in Orange
Technical Parts(Test Strategy) in Black]
What are we going to test? – The Scope
When is the testing going to happen – Schedules
Entry Criteria – When to start testing?
How?
Deliverables – Test Cases
Outputs
Communicate
Roles and Responsibilities
Tools
Test data
Defect – how to deal with them? Defect Management Process
Risks – How to handle those
When to stop testing – Exit criteria
Environment
Reports/metrics