The individual element to be tested. There usually is one test object and many test items. See also test object. A reason or purpose for designing and executing a test.

An element of configuration management - consisting of the recording and reporting of information needed to manage a configuration effectively. This information includes a listing of the approved configuration identification - the status of proposed

Acronym for Computer Aided Software Engineering.

The activity of establishing or updating a test plan.

The degree to which a component - system or process meets specified requirements and/or user/customer needs and expectations. [After IEEE 610]

Two persons - e.g. two testers - a developer and a tester - or an end-user and a tester - working together to find defects. Typically - they share one computer and trade control of it while testing.

A white box test design technique in which test cases are designed to execute combinations of single condition outcomes (within one statement).

A pointer within a web page that leads to other web pages.

The ease with which the software product can be transferred from one hardware or software environment to another. [ISO 9126]

A method to determine test suite thoroughness by measuring the extent to which a test suite can discriminate the program from slight variants (mutants) of the program.

The capability of the software product to re-establish a specified level of performance and recover the data directly affected in case of failure. [ISO 9126] See also reliability. The ability of the software product to perform its required functions