Welcome to the next episode in our new series “Integrating testing into your development flow”. Today we are going to be looking at “How to Define and Implement a Test Plan”.
In our last presentation, we discussed how to design and build a Test Strategy document. Now that that document is ready, it is time to start writing the detailed Test Plan and continue further phases of testing. In plan, we will deal with the details of the overall test coverage. Including things like features to be tested, features not to be tested, estimation, scheduling and resource management.
Not only will we be covering all the individual points in the test plan and their meaning, but we will also actually be looking at two real-world examples of how this plan is implemented and can differ between organizations. Finishing off with some excellent Q&A from our viewers as to how to approach implementing these plans in their organizations.
Topics covered in Define and Implement a Test Plan
- What is a Test Plan?
- Test Strategy vs. Plan
- Types of Plans
- How to build a good plan
- Sample templates
- Tips on Writing a Successful Document
This series comes from our mentoring/mastermind classes. These classes are virtual meetings that focus on how to improve our technical skills and build our businesses. The goals of each member vary. However, this diversity makes for great discussions and a ton of educational value every time we meet. We hope you enjoy viewing this series as much as we enjoy creating it. As always, this may not be all new to you, but we hope it helps you be a better developer.