Member-only story
Hi All, when we are working in a traditional waterfall development model where requirements are not changed as part of the first phase (which is the Requirement gathering phase) as per the client requirement, we follow Test Plan which is a crucial document for the testing especially as the name also signifies. Consider this as an example for our understanding.
The main question here is What is a Test Plan? What does it contain? Who prepares it? When it should be ready? And some more information about it. So, let's get started.
Test Plan is a detailed document that describes the different planning activities for testing to be carried out in a Software development project.
👉Test plan document details the scope, objective, testing approach, timeliness, assumptions, and risks, dependencies, resources, tools, environment requirements for the test event planned for a specific project.
👋Project scope describes the In-Scope and Out of scope areas for testing.
➡️ It also highlights the test approach for test validation for your specific project.
↪ Pass/Fail Criteria
example: All Critical, blockers and high defects should be closed.
↪ Testing suspension/Redemption Criteria
example: Smoke tests failed. or Build deployment issues.
