Software Testing Glossary

Element of a comprehensive test strategy that enables the tester to concentrate on the manner in which the application under test is able to handle exceptions.

Process of deliberate addition of known defects to those that already exist in the component or system. It is done for tracking the detection and removal level and estimating the number of defects remaining in the system.

A tool for seeding (i.e., intentionally inserting) faults in the component or system.

It is the ability of software to maintain a certain level of performance when there are software defects or when the established interface interaction is violated.

The method used to analyze the causes of defects. To find the specific defects this method models visually as the logical connection between failures, human errors and external events can be combined.

The way for which there exists a set of input values and preconditions that allow it to be executed.

Attribute of a component or system that is defined or implied in the documentation requirements (for example, reliability, usability, or design constraints).

An iterative and incremental software development process driven from a client-valued functionality (feature) perspective.

The computational model, which consists of a limited number of states and transitions between these states, possibly associated actions.

It is the review characterized by documented procedures and requirements, for example, inspection.