test-strategy-vs-test-plan A Test Test Strategy document is a high level document and normally developed by project manager. This document defines “Software Testing Testing Approach” to achieve testing objectives. The Test Strategy is normally derived from the Business e!uirement Specification document. The Test Test Strategy document is a static document meaning that it is not updated too often. "t sets the standards for testing processes and activities and other documents such as the Test Test #lan draws its contents from those standards set in the Test Strategy $ocument. Some companies include the “Test Approach” or “Strategy” inside the Test Test #lan% which is fine and it is usually the case for small projects. &owever% for larger projects% projects% there is one Test Test Strategy document and different number of Test #lans for each phase or level of testing.
Components of the Test Test Strategy document • • • • •
Scope and 'bjectives Business issues oles and responsibilities (ommunication and status reporting Test deliverables
• • • • • • •
"ndustry standards to follow Test automation and tools Testing measurements and metrices is)s and mitigation $efect reporting and trac)ing (hange and configuration management Training plan
&ere is an e*ample of an Agile Test Strategy Document Template
Test Plan The Test #lan document on the other hand% is derived from the #roduct $escription% Software e!uirement Specification SS% or +se (ase $ocuments. The Test #lan document is usually prepared by the Test ,ead or Test anager and the focus of the document is to describe what to test% how to test% when to test and who will do what test. "t is not uncommon to have one aster Test #lan which is a common document for the test phases and each test phase have their own Test #lan documents. There is much debate% as to whether the Test #lan document should also be a static document li)e the Test Strategy document mentioned above or should it be updated every often to reflect changes according to the direction of the project and activities. y own personal view is that when a testing phase starts and the Test anager is “controlling” the activities% the test plan should be updated to reflect any deviation from the original plan. After all% #lanning and (ontrol are continuous activities in the formal test process.
Components of the Test Plan document • • • • • • • • • • • • •
Test #lan id "ntroduction Test items eatures to be tested eatures not to be tested Test techni!ues Testing tas)s Suspension criteria eatures pass or fail criteria Test environment /0ntry criteria% 0*it criteria1 Test deliverables Staff and training needs esponsibilities
•
Schedule
This is a standard approach to prepare test plan and test strategy documents% but things can vary company-to-company.
Test Plan Test Strategy A test plan for software project can be Test strategy is a set of guidelines defined as a document that defines the that e*plains test design and scope% objective% approach and determines how testing needs to be emphasis on a software testing effort done (omponents of Test plan include- Test (omponents of Test strategy plan id% features to be tested% test includes- objectives and scope% techni!ues% testing tas)s% features pass documentation formats% test or fail criteria% test deliverables% processes% team reporting structure% responsibilities% and schedule% etc. client communication strategy% etc. Test plan is carried out by a testing A test strategy is carried out by the manager or lead that describes how to project manager. "t says what type test% when to test% who will test and of techni!ue to follow and which what to test module to test Test plan narrates about the Test strategy narrates about the specification general approaches Test plan can change Test strategy cannot be changed "t is a long-term plan of action.2ou Test planning is done to determine can abstract information that is not possible issues and dependencies in project specific and put it into test order to identify the ris)s. approach "n smaller project% test strategy is A test plan e*ists individually often found as a section of a test plan "t is set at organi3ation level and "t is defined at project level can be used by multiple projects •
