Software Testing
SOFTWARE TESTING
SOFTWARE TESTING
Testing is the process of executing a program with the intent of finding errors.
TESTING PRINCIPLES
All tests should be traceable to customer requirements.
Tests should be planned long before testing begins.
The Pareto principle applies to software testing. Stated simply, the Pareto principle implies that 80 percent of all errors uncovered during testing will likely be traceable to 20 percent of all program components.
TESTING PRINCIPLES
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.
TEST ORACLES
To test any program, we need to have a description of its expected behavior and a method of determining whether the observed behavior conforms to the expected behavior. For this we need a test oracle.
A test oracle is a mechanism, different from the program itself, which can be used to check the correctness of the output of the program for the test cases.
TEST ORACLES
Test oracles are human beings, so they may make mistakes when there is a discrepancy between the oracles and the results of a program. First we have to verify the result produced by the oracle before declaring that there is a fault in the program, that’s why testing is so cumbersome and expensive.
LEVELS OF TESTING
There are three levels of testing, i.e., three individual modules in the entire software system.
Unit Testing
In unit testing individual components are tested to ensure that they operate correctly. It focuses on verification effort. On the smallest unit of software design, each component is tested independently without other system components.
There are a number of reasons to do unit testing rather than testing the entire product:
The size of a single module is small enough that we can locate an error fairly easily.
The module is small enough that we can attempt to test it in some
SOFTWARE TESTING
Testing is the process of executing a program with the intent of finding errors.
TESTING PRINCIPLES
All tests should be traceable to customer requirements.
Tests should be planned long before testing begins.
The Pareto principle applies to software testing. Stated simply, the Pareto principle implies that 80 percent of all errors uncovered during testing will likely be traceable to 20 percent of all program components.
TESTING PRINCIPLES
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.
TEST ORACLES
To test any program, we need to have a description of its expected behavior and a method of determining whether the observed behavior conforms to the expected behavior. For this we need a test oracle.
A test oracle is a mechanism, different from the program itself, which can be used to check the correctness of the output of the program for the test cases.
TEST ORACLES
Test oracles are human beings, so they may make mistakes when there is a discrepancy between the oracles and the results of a program. First we have to verify the result produced by the oracle before declaring that there is a fault in the program, that’s why testing is so cumbersome and expensive.
LEVELS OF TESTING
There are three levels of testing, i.e., three individual modules in the entire software system.
Unit Testing
In unit testing individual components are tested to ensure that they operate correctly. It focuses on verification effort. On the smallest unit of software design, each component is tested independently without other system components.
There are a number of reasons to do unit testing rather than testing the entire product:
The size of a single module is small enough that we can locate an error fairly easily.
The module is small enough that we can attempt to test it in some