What are the most important components/parts of a well-written test plan document for a testing project. Consider you are testing a Financial web app.
As per IEEE 829 standards, the components of a Test Plan document should be :
- Test Plan identifier
- Test Items
- Items to be tested
- Features excluded for testing
- Testing Approach
- Test Pass and Fail Criteria
- Resumption/Suspension Criteria
- Test deliverables
- Test Environment Set Up
- Training and Staffing
- Team Member Responsibilities
- Testing Schedule
- Planning for Risks and Contingency Plans
You can read in detail about this here : IEEE 829
However it is not mandatory to include each and every thing mentioned here. I have seen many test plans missing many components from this check list. In commercial companies ( like MNC's) , there is a specified custom format, which is roughly based on these standards ( or any standard that the company follows).
Is test plan a part of overall test strategy document? Are the 2 documents merged in commercial testing projects.
A test strategy defines the overall testing approach to be followed during the testing and as such, it should be a different document, a high level definition of the testing that we are going to follow. However, it is not an unfamiliar situation, when test strategy is defined inside the test plan itself ( a practice in my current organization).
Since we are talking about an overall strategy here, so Test Plan would be an essential part of a test strategy. You can have a single high level Test Strategy document for a project and then have various test plans, which are created as per the test strategy.
A very good documented example would be this.
Please provide a real world, test plan document , if possible.
You will find a lot of such test plans on internet. A good place would be this