Give Accurate Terminology for Following System Testing Definitions Flashcards

Simulated or actual operational testing by potential
users/customers or an independent test team at the developers' site, but outside the development organization. Often employd for off-the-shelf software as a form of internal acceptance testing.

Directed and focused attempt to evaluate the quality, especially reliability, of a test object by attempting to force specific failures to occur.

Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers, to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes. It is often employed as a form of external acceptance testing for off-the-shelf software in order to acquire feedback from the market.

Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system without reference to its internal structure.

Testing, either functional or non-functional, without reference to the internal structure of the component or system.

A black box test design technique in which test cases are designed ATA based on boundary values. See also boundary value.

A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system.

An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g. statement coverage, decision coverage or condition coverage.

A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.

A software tool that translates programs expressed in a high order language into their machine language equivalents. [IEEE 610]

The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify. See also cyclomatic complexity.

The testing of individual software components. [After IEEE 610].

A tool that provides support for the identification and control of configuration items, their status over changes and versions, and the release of baselines consisting of configuration items.

Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.

A sequence of events (paths) in the execution through a component or system.