A Test Planning is the initial stage that is used by us before we start working on any testing project.A Test Plan Document is prepared which basically contains all the necessary actions & procedures that are needed for the execution of testing.
As Per WikiPedia Definition : A Test Plan is a "A test plan is a document detailing a systematic approach to testing a system such as a machine or software. The plan typically contains a detailed understanding of what the eventual workflow will be."
I define them as "It is a guiding document for any testing project. It is important that a Test plan goes for a review and update itself with the review comments."
Identify and select testers for Testing
Develop test scenarios and scripts/cases
Validate participants availability for testing
Review scenarios/scripts for accuracy, completeness and sequence
Ensure Testing configuration for testing activities
Testing environment validation
Testing by Testing participants
6.Assumptions and Risks
Assume#2:The Business team has reviewed and accepted functionality identified in the
business requirements and software requirements documents.
Assume#3:Code walkthroughs/reviews will be completed by the development team.
Risk #2 - Knowledge and the Mitigation plan is to attend required trainings and update the knowledge.
Risk #3 - Timelines and Mitigation Plan is to have the necessary resources and also incase the timelines is not feasible speak out earlier rather than in the end.This will avoid confusion.
Once the project is completed the Test Manager will sign in the section and also specifying to state that the testing is complete and the quality is ensured it is ready for use.
Once we have the test plan it is important we share it across the senior management and also with respective people who are related with the project. This will make way for clear transition among people working in the project and also the testing goals of the project will be very clear.