Informaciones emergentes

Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test.

Execution of the test process against a single identifiable release of the test object.

A test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned. See also test management.

An item or event of a component or system that could be verified by one or more test cases, e.g. a function, transaction, feature, Quality attribute, or structural element.

During the test closure phase of a test process data is collected from completed activities to consolidate experience, testware, facts and numbers. The test closure phase consists of finalizing and archiving the testware and evaluating the test process, including preparation of a test evaluation report. See also test process.

A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify Compliance with a specific requirement. [After IEEE 610]

All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by way of formal amendment procedure, then the test basis is called a frozen test basis. [After TMap]

The process of analyzing the test basis and defining test objectives.

A set of one or more test cases. [IEEE 829]

A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and Graham], [IEEE 1028] See also peer review.