Software Testing Principles.
Some testing principles are:
All tests should be traceable to customer requirements As we have seen, the objective of software testing is to uncover errors. It follows that the most severe defects (from the customer’s point of view) are those that cause the programme to fail to meet its requirements.
Tests should be planned long before testing beings Test planning can begin as soon as the requirements model is complete. Detailed definition of test cases can begin as soon as the design model has been
The Pareto principle applies to software testing Stated simply, the pareto principle implies that 80% of all errors uncovered during testing will likely be traceable to 20% of all programme components. The problem, of course is to isolate these suspect components and to throughly test them.
Testing should begin ‘in the small’ and progress toward testing ‘in the large’ The first test planned and executed generally focus on individual components. As testing progresses, focus shifts in an attempt to find errors in integrated clusters of components and ultimately in the entire system.
Exhaustive testing is not possible The number of path permutations for even a moderately sized programme is exceptionally large. For this reason, it is impossible to execute combination of paths during testing. It is possible, however, to adequately cover programme logic and to ensure that all conditions in the component-level design have been exercised.