Guideline: Defining Test Techniques |
This guideline describes how to document a test technique.
Main Description
For each existing or required technique: Define objectives and scope Describe the implementation method Identify suitable evaluation methods Identify applicable uses of automation Identify applicable tools #### Define objectives and scope Many techniques will support more than one type of testing, so give some thought to identifying which tests the technique will need to support. This helps to identify the scope of the effort required if the technique is being defined for the first time. Give thought to the underlying objective and value this technique represents. #### Describe the implementation method Define how the technique will be implemented. It is not good enough to simply state "We are doing system performance testing": You need to give serious thought to how that can be achieved. Some techniques you would like to use will be uneconomic to pursue. By describing briefly how you will approach implementing this technique, you will be able to get an overall sense of the logistics involved, and the practicalities of pursuing the technique further. #### Identify suitable evaluation methods Determine how you will observe and evaluate the results of each test implemented using this technique. Give thought to the different test oracles that are available for you to use: Is there a single oracle, or are their different ways that you can determine the result of each test? #### Identify applicable uses of automation Automation can play an important role in many test techniques. In some cases, it will be less sophisticated, simply providing support for conducting manual tests. Give some thought to how the work involving the technique could be most efficiently implemented, maintained, and managed. Be open minded: Think both broad and deep, considering as many options as possible. #### Identify applicable tools Identify the appropriate tools to use with this test technique. Use the work from the previous step that identified uses of automation. Remember to consider a broad range of tool categories: your list of candidate tools should include more than just test execution automation tools. Consider tools that will enhance the productivity of the test team by reducing repetitive, laborious tasks, such as Test Data management, Test Results analysis, incident and Change Request reporting tools, and so on.
© Copyright IBM Corp. 1987, 2009. All Rights Reserved.