Red Bar
Navigation:: Home >> Test and measurement >> this page

Test Strategy Document & Template

- template and instructions for a test strategy document, showing how it can be used and implemented..


Test strategy tutorial includes:

    •  Test strategy development
    •  Test strategy example
    •  Test strategy document

In order to define a test strategy and have it reviewed by all interested parties and agreed, it is necessary to write a test strategy document.

A test strategy document template is given below. The test strategy document template defines some sections that could be used for a test strategy document. Naturally this is only a general template, and will need to be adapted for the particular circumstances and requirements.


Test strategy document template / sections

The test strategy document template can include the following sections and subsections:

  • Header and company standard initial sections:   This section will include the company header and initial pages. They will include elements such as the review and release / issue history.
  • Abbreviations:   A table of all abbreviations used within the document needs to be included to ensure that any abbreviations used are defined to prevent any misunderstanding. In addition to this, the first time any abbreviation is used, the full version should also be used in line with good technical document writing practice.
  • Introduction:   This section will comprise a number of subsections that will, as a whole, set out the initial information for the reader to understand what is being addressed. The subsections addressed may include the following:

    • Initial outline:   At the very beginning of the document it is necessary to outline the basic situation and what is to be addressed and why. It will effectively state the requirement in very broad terms. This will enable the reader to understand what is being addressed within the document.
    • Applicability and scope:   This will detail areas to be included within the document stating what the document is applicable to as well as detailing any limits to the application of the document.
    • Document structure:   This section will detail the structure of the document, giving a short view of what each section contains.
    • Referenced documents:   A full list of all referenced documents should be given. Where applicable, their location should also be listed.
  • Requirements:   This section will give a more in-depth view of the requirements. It will detail the product and detail the area to which the test strategy will apply in detail.
  • Product description:   It may be worth providing a review of the product itself. This could detail each assembly within the product detailing and features that may need to be addressed specifically from a testability viewpoint. Within this section, anticipated yields and volumes can be specified.
  • Examination of current situation:   It may be necessary to look at the starting points and what equipment and space is available for the testing area. With cost often a major issue, re-use of existing test equipment and facilities may be an issue. If the test strategy is to apply to a new product, it may be that the testing will need to sue an area where another products, each with their own test strategies are currently tested. These issues will impose constraints on how any new test strategy, or a test strategy for a new product can be implemented.
  • Proposed strategy overview:   This section of the test strategy document can detail the test strategy to be adopted. It should address the different forms of testing to be used, and at what stages. It should also take on board the expected yield rates and sue this to not only determine the types of test to be used, but analysing the required throughput and the expected test times it can detail the number of test stations required at each stage of testing.
  • Test strategy for individual assemblies:   Dependent upon the nature of the product, its complexity and the number of assemblies, it may be worth detailing the test strategy for each assembly and sub-assembly within the overall product in a separate section to the one above. It can detail each subassembly:

    • Assembly A:   Details should be provided for the method or methods used for testing the assembly.
    • Assembly B:   Details should be provided for the method or methods used for testing the assembly.
    • Further assemblies as required ..:   .. details supplied for each assembly...
  • Summary and recommendations:   This section will summarise the document, bringing together the overall recommendations. It will propose a way forwards, summarising aspects including lead times, test development required, investment in new equipment, and the overall costs. It is also useful to include a return on investment calculation to justify the expenditure.

This test strategy document template is only a proposal and will need to be adjusted for the given circumstances and company requirements. It should be taken as a starting point to develop the test strategy document that will fulfil the requirements of defining the test strategy while meeting the overall company requirements.

By adopting a sound test strategy from the early design stages of a product, production costs can be kept to a minimum while maintaining a high quality product. This is exactly where some of today's top manufacturers score, and are able to deliver cheap reliable product.


<< Previous   |   Next >>



Automatic test, ATE, technologies . . . . .

ATE basics PCB inspection ICT, In-Circuit Boundary scan
Flying probe Functional, FATE Test Strategy DFT