It is a document prepared by managers or leads which consists of all the activities related to testing, once the requirements are given the managers and lead study the requirements and prepare the test plan.
The test plan is followed by all the test engineers for the further testing activities.
The Test Plan consists of following attributes:
7.Machine configuration and Test environment
8.Roles and Responsibilities
14.Entry and Exit criteria
The objective defines the aim of writing the test plan.
For eg: objective - This Test Plan for Cheetah- 2.0 ICICI.
Features which need to be tested and the features which do not need to be tested are mentioned under scope.
For eg: Scope - Features need to be tested(In Scope) - Login, Compose, Inbox. Features not to be tested(Out of scope) - facebook.com, help.
Here the flow of the application is represented or written in the form of flow charts or scenarios to understand the flow of the application.
The types of testing activities need to be performed for the application are mentioned in testing methodologies.
For eg: smoke testing, functional testing, Integration testing, System testing, Usability testing, Compatibility testing.
All the time schedules for the testing activities will be mentioned in this section.
The templates which are followed by the test engineers are mentioned here.
For eg: Test case template, Test case review template, Bug report template and RTM.
Machine configuration and Test environment
The configuration with respect to Test engineers machine as well as the test servers are mentioned in this section.
For eg: (i) Test Environment:
S/w: OS, WS, AS, DB.
H/w: RAM, HDD, Processor.
Role and responsibility of whole QA team is mentioned here, role is the designation and responsibilities is the work to be done.
(i) Role: Team Manager
Responsibilities: Prepare/Review test plan, Meeting with development team/B.A, Deciding schedules, Handling escalation.
(ii) Role: Test Lead
Responsibilities: Prepare/Review test plan, assign tasks, preparing templates, approval of test cases, preparing reports, handling escalation, conducting meetings.
(ii) Role: Test Engineer
Responsibilities: Understanding requirements, writing/review test cases, executing test cases, preparing RTM with respect to their modules, defect tracking.
All the tools with respect to current release are mentioned in this section.
For eg: Defect tracking tool Bugzilla 3.0
All the assumed problems that may occur during testing process are mentioned in this section.
All the assumed risks that may cause some damage are mentioned in this section.
It is a back up plan prepared to avoid assumed risk. For eg: Assume that if one test engineer leaves the job then their is a risk that the quality of the module will not be good, so they do mitigation plan which is a back up plan in which they give primary contact and secondary contact.Primary contact is the test engineer who is working on his module and he become secondary contact for the module on which other test engineer is working.
The supporting documents handed over to the customers along with the application or software are called deliverables.
Following deliverables are there:
1. Test cases.
2. Test scripts.
3. Test Execution reports.
5. Other reports.
6. Release notes - user manual, installation procedure, platform on which software work.
7. List of existing bugs in the current release.
8. List of fixed bugs from the previous release.
Entry and Exit criteria
It indicate the criteria for starting and stopping testing.
The entry criteria for testing would be - coding should be completed, all the test cases should be ready, build should be installed on test server and necessary resources should be ready.
Similarly the exit criteria for testing would be - All the test cases should be executed, majority of the test cases i.e, 95%-97% of the test cases should be passed and there should be no blockers or critical or major bugs where as some 3-4 minor bugs are allowed.
Here the managers derived or estimates the efforts required by the test engineers in the form of time , cost and response. Generally it is done by using effort estimation techniques like:
1. Work breakdown approach.
2. Delphi technique.
3. Base on Functional point.
4. Base on Kilo lines of code(KLOC).
5. Use case based approach.