Test plan preparation for Manual Testing

Test plan is a document which covers all the future testing activities in the project and it covers all this

1. objective: aim of  the project
2. scope:here they will decide which all features to be tested and which all features not to be tested
   example:gmail application is given,here we will test login feature, logout , compose, draft, trash,etc….so this are the features to be tested.But here also helpfeature will be there, this help feature will be tested by the technical writter, so no need to test this.Like wise, for every application we will decide the scope of the application.
3. Approach:It is way we go about tesing the product.
   1. high level testing
      going to login feature, testing each field in that ,covering that particular feature and going for next feature like composeand etc….the testing continous
   2. writing the flow chart for testing the product.

4. Testing methodology:In the future when the product given for testing,what all testing should be done will be decided here.
   Testing like fuctional, integration, system, adhoc, smoke, etc….
5. Testing Environment:Here they will decide what all the hardware and software to be required to set up the testing environment when the product given to them
6. Defect Tracking:Here we will decide how to track the defects and also the
   1. defect tracking tool
   2. severity
   3. test management tool:to store the defects
      All will be decided
7. Assumptions,Risks,Mitigation plan:here they will assume something if that assumption goes wrong, then it will be risk and finally they will do mitigaiton plan to overcome the risk
   Example:
   Assumption:got one new project,allocated work to every test engg assuming everyone will one will be there till the end of the project
   risk:one person quites the job, so assumption goes wrong, and it is risk nowmitigation plan:so does the mitigation plan to overcome this plan in the test plan stage itself.
9. ETVX {Entry-Task-Validation-Exit} criteria are to be mentioned. Entry means the entry point to that phase. For example, for unit testing, the coding must be complete and then only one can start unit testing. Task is the activity that is performed. Validation is the way in which the progress and correctness and compliance are verified for that phase. Exit tells the completion criteria of that phase, after the validation is done. For example, the exit criterion for unit testing is all unit test cases must pass.
10. Roles and Resposibilities:
    what are the roles and resposibilities of the P.M, T.L,T.E’s will be decided,like who shoul write the testplan , testcase, reveiew testplan testcase, execute testcase, auotmate test case, everything will be decided
11. Deliverables:This the outputs from the testing team
    1. test report
    2. tracebility matrix
    3. defect tracking report
    4. graphs and metrices
       graphs:like defect tracking graph, defect distribution graph.so that we can track which module is having more bug and also how much testing we have completed , how much yet to be completed, everything can be tracked
    5. release notes:release notes are those which they will release along with the product.It consists of
       1. what all features are tested/not tested
       2. Addition/modification/deletion of features
       3. bugs which are found in previous release and fixed in current release
12. Automation
    1. what all features to be automated and not to be auotmated
    2. which automation tool to use will be decided
13. Template:Here all the standard templates will be stored for all the documents like test case, review template,tracebility matrix, test report, etc…So when ever the T.E is filing the document he /she should use this standard templateTest Plan template
    

    version	Author	Reviewer	Comments	Approve by	Approved date
    Which versionshd be mentioned	Name of the test engineer,who’s logging the defect

So this all I know about Test plan…I guess this may help u…