Software Testing Glossary

Approach to software development, in which the code is written by two programmers at one computer. This presupposes ongoing review of the code.

Two people working together to find software faults. It may be either two testers, a developer and a tester, or an end user and a tester. Usually they are working at one computer,  passing control of it to each other in the process of work.

A form of integration testing that targets pairs of components that work together, as shown in a call graph.

Software development by black box method, in which test cases are designed in such a way as to meet all the possible separate combinations of each pair of input parameters.

Testing technique which has the purpose to ensure that a new application which has replaced its older version has been installed and is running correctly.

A statistical technique in decision making that is used for selection of a limited number of factors that produce significant overall effect.

The test is considered to be passed if its actual results match the expected results.

The rules for determining whether a test element passed a test or not.

Testing technique that consists in monitoring results of a running system without introducing any special test data.

The sequence of events (such as executable statements) in the component or system from input to output.