Limited 20% Scholarship- Use Coupon - JAN20
To find out the difference between Test Strategy and Test Plan, let us first understand the individual concepts in brief.
Test Strategy is a high-level document that defines the proper approach for software testing. It is basically derived from the Business Requirement Document (BRD). It is developed by the business analyst or project manager. It is a static document that sets the standards for the testing and not updated often.
Test Plan is derived from the Software Requirement Specification (SRS) that is developed by the project manager or test lead. It is designed with an objective to include all details related to the testing like what to test, how to test, when to test, and who will be testers etc? A Test Plan is updated frequently as soon as new features or changes are introduced.
Let us see the quick differences between the two concepts before going to detail:
|Test Plan||Test Strategy|
|A Test Plan for the software project is a document that defines the scope, objective, approach, and emphasis more on the software testing efforts.||Test Strategy is defined as the set of guidelines that explain the test design and regulates how testing needs to be done.|
|The major components of Test Plan include – Test Plan ID, test environment, features to be tested, entry/exit criteria, status, type of testing, brief introduction etc. We will discuss each of these components in detail below.||The major components of Test Strategy include – Scope, Objective, business issues, risks, testing approach, testing deliverables, defect tracking, training, automation etc. We will discuss each of these components in detail below.|
|A Test Plan is developed by the project manager or test lead.||A Test Strategy is developed by the business analyst or project manager.|
|Test plan narrates about the specification and it can be changed frequently.||Test Strategy narrates about the general approaches and it not updated often.|
|A Test Plan usually exists individually.||Test strategy is divided into multiple test plans that are taken care further independently.|
|It is defined at the project level.||It is defined at the organization level.|
|Test planning helps to identify the possible risks or issues.||A test strategy helps to abstract information that does not project specific but it can be used with the test approach.|
In this section, we will discuss the major components of Test Strategy and what exactly it contains.
In this section, we will discuss the major components of the Test Plan what it contains.
Basically, the test strategy defines the approach for testing and test plan has all the detail how this approach can be executed successfully in a properly planned way. They both go hand in hand. Moving ahead, let us discuss do we need a test plan for an agile project too?
As we know, test planning is an important activity of a testing process and one requires careful thoughts and decisions not from test manager but all members of the testing team and product manager too. A test manager or product manager is responsible for designing a test plan in case of a software project.
Most organizations believe that the test plan is the most important part of the testing process and spend many hours or efforts to come up with a great test plan. Test books dedicate a complete section to test planning, how to write a comprehensive test plan in order to approve a product.
In the real world, in a waterfall environment, a test plan document is mostly seen during the life-cycle of a product. However, the test planning and monitoring is an ongoing activity during the project life-cycle and it needs to be updated frequently as soon as new features or changes are made.
As test planning is always considered as a must-have product in the waterfall project, do we really need a test plan for an agile project too? Does it really add value to what the whole team is trying to achieve?
In the agile environment, the contents of a release are discussed before the Sprint so the testing team should know in advance what is the scope and what should be tested. Also, this is necessary to check the estimate how much time it will be taken by the team to complete the testing including environment, setup, scenarios, automation, exploratory, performance etc.
In the story writing session, the testing team starts with writing scenarios in advance to cover many ways how stories can be tested. This is the most valuable step for the team. During the sprint, The QA team is continuously testing new code or features.
Testing planning becomes a dynamic activity based on priorities for the day change. Testing is based on what is the activity for the day and the outcome of the day before. This is clear from the discussion that test plans don’t reveal defects but test scenarios will. The efforts are shifted to creating best test scenarios instead of creating a test plan.
So, what we really need here a short agile strategy document outlining the processes or test cases applicable across Sprints like test environment, test planning, workshops, manual testing, automated testing, test reports, staging, test coverage etc. These are the processes or activities applicable to every Sprint but derived by Company vision only. With this discussion, it must be clear to you that we need an agile test strategy for the agile project that is further divided into test cases or test plans based on convenience.
Moving ahead, let us discuss how test case, test plan, and test strategy are written for a software project.
However, test case, test plan and test strategy all three are dependent. A test case is used in the test strategy which in turn used in the test plan. Test plan or test strategy are prepared by different people but their outputs are cumulative of their inputs.
JanBask Training is a leading Global Online Training Provider through Live Sessions. The Live classes provide a blended approach of hands on experience along with theoretical knowledge which is driven by certified professionals.