Pre conditions are important
project status, project size, project duration, dead line, team size,
then start test plan what to test ? who will test? why will test? when it will test? how it will test?
Thanks for the input Sumit, Sarang and Shashikant
Sumit: There are some companies which rely on Test Plan. For some companies often test strategy document is often a part of Test Plan.
In general, even if I have to write Test Strategy , I would need some inputs : For exmaple : Project Schedule, Project Plan, Project size, Duration. Again as you said discussions with BA and other Test Team members would be critical.
1. First, get the SOW[ State of work] if you are working in service company and Get the base-lined requirement if you are working in Product company
2. Ask for the schedule for the cycle.
3. Get the testing scope for the iterations and work on that.
4. Estimation for the resources[Team members] if you the project is being developed newly.
5. Find out the risks
6. Understand the dependencies.
TEST PLAN would be started during the END of the Requirement Phases.
Correct me if i am wrong.
Does that mean it is done after the functional requirements are ready.
Because I felt you need to have complete requirements before a test plan is created.
If you just have partial requirements or during the requirements gathering phase, would it be possible to write a test plan?
is a document is a procedural guide which describes the Objectives, Scope, Test Approach, Strategy and Schedule of the intended testing activitiesIt identifies the Test items, the features to be tested, the testing tasks, timelines,
who will do each task, any risk requiring contingency plan, to what level the tests will be performed etc.
The three major elements of a test plan document are Test Coverage, Test Methods, and Test Responsibilities.
Test Coverage in the test plan states what requirements will be verified during what stages of the product life. Test Coverage is derived from design specifications and other requirements.
Test Methods in the test plan state how test coverage will be implemented and what kind of test methodologies will be implemented during the entire QA phase. Test methods also specify test equipment to be used in the performance of the tests and establish pass/fail criteria.
Test Responsibilities includes what test methods needs to be performed at each stage of the product life. This allows test team to plan, prepare test equipments and other resources necessary to implement the test methods.
Test responsibilities also includes, what data will be collected, and how that data will be stored and reported
(often referred to as Deliverables)