Testing Tactics

Testing Fundamentals

•        All tests should be traceable to customer requirements.
•        Tests should be planned long before testing begins.
•        The Pareto principle applies to software testing.
•        Testing should begin “in the small” and progress toward testing “in the large.”
•         Exhaustive testing is not possible. 
•        To be most effective, testing should be conducted by an independent third party.

Testing Principle   

•        All tests should be traceable to customer requirements.
•        Tests should be planned long before testing begins
•         The Pareto principle applies to software testing.
•        Testing should begin “in the small” and progress toward testing “in the large.”
•         Exhaustive testing is not possible.
•         To be most effective, testing should be conducted by an independent third party.

Testing Objective

• Primary Objective
• But testing cannot show the absence of errors and defects, it can show only that software errors and defects are present. 
• Data collected as testing is conducted provide a good indication of software 
• reliability and some indication of software quality as a whole.
• A successful test is one that uncovers an as-yet-undiscovered error
• A good test case is one that has a high probability of finding an as-yet undiscovered error
• Testing demonstrates that software functions appear to be working according to  specification, that behavioral and performance requirements appear to have been met.
• Objective is to design tests that systematically uncover different classes of errors and to do so with a minimum amount of time and effort.
• Testing is a process of executing a program with the intent of finding an error.