Software Testing Glossary

The ability of software to be modified in some way if it is necessary.

An experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified.

A tree indicating hierarchical ordered equivalent areas that used to develop test scripts in the classification tree method.

Development of tests using a black box method, in which test cases, described by means of a classification tree, are designed to test sample combinations of input and/or output subsets.

The ability of the software to co-exist with other independent software in a common environment, sharing common resources.

Computer instructions and data definitions expressed by programming language or in the form of output data of collector, compiler or other translator.

The method of analysis that determines which parts of the software have been tested by a set of tests, and which haven’t been.

Testing technique that uses testing frameworks (such as xUnit) that allow the execution of unit tests to determine whether various sections of the code are acting as expected under various circumstances.

Excessive emotional or psychological dependence on another person, specifically in trying to change that person’s current (undesirable) behavior while supporting them in continuing that behavior.

A means to identify a suitable subset of test combinations to achieve a predetermined level of coverage when testing an object with multiple parameters and where those parameters themselves each have several values, which gives rise to more combinations than are feasible to test in the time allowed.