The development of a test strategy is a means of communication with the customer commissioning the test on such matters as the organization of testing and the strategic choices that go with it. The test strategy indicates how testing is to be carried out. In order to make the best possible use of resources and time, it is decided on which parts and aspects of the system the emphasis should fall. The test strategy forms an important basis for a structured approach to testing and makes a major contribution to a manageable test process.
The customer who commissions the test will expect specific qualities of the system when in production, and wants to know whether the released system will meet these requirements. If the system qualitatively does not meet the requirements or only to a limited extent, this implies high damage for the organization, for instance since high rework costs will be needed or clients/users will be unsatisfied. Therefore, this situation forms a risk for the organization. 'Risk' in this paper is defined as:
A risk is the chance of an error  occurring (chance of failure) related to the damage expected when this error does occur
Testing covers such risks by giving insight into the extent to which the system meets the quality demands. When quality turns out to be insufficient timely measures can be taken, e.g. rework by developers. If the shipping of the system implies many risks for the organization, better testing is obvious as a solution. And the reverse also holds: