A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. A complex system may have a high level test plan to address the overall requirements and supporting test plans to address the design test plan and test strategy pdf of subsystems and components. Test plan document formats can be as varied as the products and organizations to which they apply.
There are three major elements that should be described in the test plan: Test Coverage, Test Methods, and Test Responsibilities. Test coverage in the test plan states what requirements will be verified during what stages of the product life. Test coverage is derived from design specifications and other requirements, such as safety standards or regulatory codes, where each requirement or specification of the design ideally will have one or more corresponding means of verification. Test coverage for different product life stages may overlap, but will not necessarily be exactly the same for all stages. For example, some requirements may be verified during Design Verification test, but not repeated during Acceptance test.
Test coverage also feeds back into the design process, since the product may have to be designed to allow test access. Test methods in the test plan state how test coverage will be implemented. Test methods may be determined by standards, regulatory agencies, or contractual agreement, or may have to be created new. Test methods used to verify hardware design requirements can range from very simple steps, such as visual inspection, to elaborate test procedures that are documented separately. Test responsibilities include what organizations will perform the test methods and at each stage of the product life. This allows test organizations to plan, acquire or develop test equipment and other resources necessary to implement the test methods for which they are responsible.
One outcome of a successful test plan should be a record or report of the verification of all design specifications and requirements as agreed upon by all parties. This page was last edited on 11 January 2018, at 11:18. Our popular software testing questions and answers series is back again! In today’s article we are going to answer difference between test plan, test strategy, test case, test script, test scenario and test condition. Software Testing Help » What is Difference Between Test Plan, Test Strategy, Test Case, Test Script, Test Scenario and Test Condition? What is Difference Between Test Plan, Test Strategy, Test Case, Test Script, Test Scenario and Test Condition?
Submit it in the comment section below or use the contact form. We almost have an overload of technical terms when working in an IT environment. There are processes, documents, tasks and everything else that is addressed by its own technical name. Now, how are we to remember, understand and use them in the right context every single time?
I always tell our participants that with an experience we hardly notice these words and that they become a part of our vocabulary. But often, confusion surrounds these and in this article today I am trying to define few commonly used terms. What is a difference between Test plan and Test strategy? What is a difference between Test case and Test script?
What is a difference between Test scenario and Test condition? What is a difference between Test procedure and Test suite? The test plan is a term and a deliverable. This is also a deliverable and also a document at that. Test strategy outlines the testing approach and everything else that surrounds it. It is different from the test plan, in the sense that a Test strategy is only a subset of the test plan.