Test Strategy how to create a powerful test strategy? Let us begin with discussing, What is a test strategy? As you know, strategy means using the resources at ones disposal to achieve the desired objectives effectively. The strategy means a plan that details how the testing objectives would be met effectively. Like any other strategy, the test strategy may be defined at different levels. You may have a Test strategy at the organization level at a program level or at a project level. The thing is that it may not be called a “test strategy” at the organization or department or program level. it may just exist as a management policy or as a part of a governance plan. At the project level, the test strategy may just be part of the test plan. Further, depending on the nature of the project, the test tragedy defined at the project level may or may not satisfy the test strategy outlined at a higher level before. What are the advantages of an effective test strategy? The advantages are it mitigates the risk to objective testing. It helps focus on different aspects of the system under test by using distinct test phases such as unit testing, integration testing, system testing and so on. Test strategy provides clarity on the required people, procedures, tools, and infrastructure. Test strategy can be used to communicate the test approach to the various stakeholders such as clients project or test managers, developers and testers in the project. If you want to define the powerful test strategy for your project or program or organization, you should consider the following tips. 1) Before you define your test strategy, you should research the clients and the end-users with respect to their needs and expectations from the application. 2) Your test strategy should aim at satisfying just the test objectives. 3) You may need to create two versions of your test strategy, depending on the situation – one for communicating to all and a detailed tailored test strategy for agreement with the key stakeholders. 4) You have the option of having different kinds of focus in different test phases. But do not go overboard with defining too many test phases with overlapping effort. In other words, economize with the test phases. Define only the ones which you think are really required. 5) Your test strategy should be totally customized according to your specific situation. What has worked for other companies or what has worked for your company in the past may not apply to your current situation. 6) You should consider the required test environment while designing your test strategy. You should have at least one test environment. That is the same or is the replica of the production environment in which the system is going to work. Further, your test strategy should resume the most common test environment configurations for the most part. 7) Your test strategy should define the testing tools for testing, defect management system or automated testing. It is best if you evaluated the testing tools yourself. If not, base your decision on choosing the testing tools (reliable or vendor-agnostic tools) on the popular user reports. 8) You should look at any defined test processes. For example entry criteria, suspension criteria, resumption criteria, exit Criteria for tests. The process to execute the test cases and the process to reporter a defect etc. to examine their feasibility in your situation. Ideally the required test processes for you that will be reused modified or created from scratch. 9) Identify the data that will be recorded, measured analyzed and reported to show the progress of your testing. 10) Challenge all assumptions while you design your test strategy. Provide safeguards if any of the prior assumption is proved incorrectly later. And finally, remember that a powerful test strategy is never static. You should monitor the results obtained from the test strategy and do not hesitate to make the desired modifications your test strategy.