Start trefwoorden te typen om de site te doorzoeken. Druk enter om te verzenden.
Generative AI
Cloud
Testing
Artificial intelligence
Security
What is a test plan?
A test plan is a document that we use to describe the test. It can contain topics on ‘what do we need to test’, ‘who will test what, and at what moment’, ‘how will we test’, ‘how much time will testing take’, ‘when is the test done’, ‘how can we organize and manage testing’, … and many more.
We use the test plan to communicate the test planning to the stakeholders for the test. It can have many different shapes and sizes, as long as it solves the problem at hand: describing the test approach and building support from the stakeholders for this approach.
The value of test planning lies in communicating about these topics with relevant stakeholders. The essence of ‘a test plan’ are the topics, not the tangible form.
When putting together ‘the test plan’, ask yourselves the questions:
So, depending on its target group and purpose the form of a (part of a) test plan varies from a sketch on a whiteboard via a section with test topics integrated in an overarching project or sprint plan to a comprehensive, separate document with many pages. So sometimes there is no separate, tangible plan at all.
All stakeholders of testing can be involved: the client, end-users, accepting parties, developers, suppliers of test environments and tooling and the testers. Make sure that the content of your communication is relevant to the recipient. If this means splitting up your test plan in several distinct artifacts, then do so!
Without being exhaustive, the test plan can consist of any and all of the following:
A test plan is a means for communication, so all the ‘usual’ success factors for effective communication apply:
Templates of a Master Test Plan (MTP) or a Detailed Test Plan (DTP) are found in the download section.