Test Plan

To watch in YOUTUBE, click here

Test Plan(Test Planning) in Software Testing

Test Plan is a detailed document about the testing process to be carried out. It includes the detailed information about testing objectives, estimation , activities, resources and schedule etc.

A Test Plan includes below information:

1. Objectives
2. Approach
3. Resources
4. Software
5. Hardware
6. Environments
7. Test Schedule
8. Deliverables
9. Responsibilities
10. Features to be tested
11. Features not to be tested
12. Entry and Exit criteria
13. Risks and contingencies
14. Pass Fail criteria
15. Estimation of time / cost
16. Assumptions and Dependencies
17. Approval Criteria

Objectives:
This talks about the objectives , the goal of the testing.

Approach:
It defines the testing steps, methods, types, testing process or techniques.

Resources:
This talks about the resources required in terms of technical skills, number of resources , team structure, size etc.

Software:
This talks about the software or application , database , web services, network configurations , operating systems etc required for testing.

Hardware:
This talks about the required hardware , machines , Virtual machines etc.

Environments:
This talks about the number of testing environments required for the testing. We might require more than one testing environments based on functionalities, properties, dependencies.

Test Schedule:
This talks about the test schedule,  how much time we need, when we will start and complete the testing.

Deliverables:
These are test documents or reports or other testing artifacts which testing team gives to the stakeholders. The artifacts are given before the testing , during the testing and after the testing.

Responsibilities:
It defines the roles and responsibilities of the team members.

Features to be Tested:
It is the scope of testing. It defines the list of the features  of the software or the  product,  which are in scope. The features mentioned in this section will be tested.

Features not to be Tested;
This also talks about the scope of the testing. It defines the list of features of the software or product which are out of scope of the testing. They will not be tested.

Entry and Exit Criteria:
Entry Criteria defines the conditions or requirements to be fulfilled before starting the testing. Such as availability of all software , access to the testers , test data, test environment being up and running etc.
Exit Criteria defines the conditions or requirements to be fulfilled before declaring the test as complete. Such as deadlines, coverage of requirements and functionalities , no defects left at the end etc.

Risks and contingencies:
Every project is associated with some risks, you should be ready for possible risks and should have proper mitigation plan for them. The risks are assumed based on previous experience, information and result. The common risks are: lack of resources, lack of software or hardware , lack of skill , late delivery of the code, change in the requirement, risk of budge/cost or time etc.
When the risk takes place, then you should come up with the appropriate solution. Some common actions for the risks are : shifting the delivery date(this is not recommended though) , changing(usually reducing the functionalities for testing ) the scope of testing, adding resources etc. For the kind of risk, if appears, whichever step is most appropriate , that step will be taken.

Pass Fail criteria:
It is a minimum standard or criteria for completing the test. To mark the test as PASSED, the criteria should be fulfilled. Such as , the product should be defect free or sometimes it will be acceptable with minor defects. This does not talk about individual test result, it talks about the testing of the overall product or software under test.

Estimation of time / cost:
Time : It talks about the time required to complete the testing , in other word, the deadline to complete testing.
Cost : It is the budget for the testing.

Assumptions and Dependencies:
It is part of risk management. The risks are future unexpected events which might occur. So, you make proper assumptions based on your experience, information and result.
The testing activities might be dependent on so many factors such as data, environment, resources, proper coordination especially when the team members are not working from the same place. You have to prioritize and carryout  the testing activities accordingly.

Approval Criteria:
You will need approval of the test plan and other deliverables at different stages of testing(before testing, during testing, after completing the testing). The client or stakeholders can approve the test plan or the deliverables. You take the approver's name , role, signature and approval date.