Testing strategy, or testing methods – is the systematic methods used for the selection and / or create tests that should be included in the test kit. It can be random inputs, test aimed to check my suspicions, a test designed to check your suspicions, the test is aimed at checking compliance with the requirements, the test is aimed at checking the distorted ™; tests that we ran last time, tests that are different from the tests that we carried last time. We choose a strategy such that there are rules by which we can determine, by this test strategy, or does not satisfy. In principle, the strategy should be programmable.
The strategy is effective if the tests included in it, with high probability find the error test object. Effectiveness of the strategy depends on a combination of nature and the nature of test errors, searching for which these tests are aimed. As in war and in business, there exist effective and ineffective strategies. Moreover, since the object is changed to correct errors and increase its capacity, the types of errors, found the object, change over time and, therefore, changing the effectiveness of the strategy. While it is theoretically possible that the strategy in relation to specific sites is improving over time, in fact, the effectiveness of most strategies over time decreases.
The strategy of the behavioral test based on the specifications. For example: a test of all the characteristics mentioned in the specification, the implementation of all the dirty tests derived from requirements. Testing performed by a strategy of behavioral test, called behavioral testing. Behavioral testing is also called black-box testing. For behavioral testing is also used the term functional testing. " When the behavioral testing (in principle, but not in practice) do not necessarily know how the object was designed. The theme of this book, behavioral testing (black box testing).
Strategy of structural tests determined the structure of the test object [BASI87, BEIZ90, NTAF88, OSTR96]. For example: the implementation of each operator at least once, the performance of each branch at least once, testing the use of all data objects, each command object program obtained by compiling. Testing performed by a strategy of structural test, also called glass box testing or white-box testing. Strategy for structural test requires full access to the structure of the object – that is the source code. This book only scratches the surface of the structural testing methods.
The strategy of the hybrid test is a combination of behavioral and structural strategies [CLAR76, RICH81]. Behavioral, structural, and hybrid strategies do not contradict each other, and neither one of them can say it better than others. Modules and low-level components are often tested using structural strategy. Large components and systems primarily tested using behavioral strategies. The hybrid strategy is useful at all levels. There is no best strategy, since the usefulness of the strategy depends on the nature of the test object, the nature of errors of the object and the level of your knowledge.