dynamic testing

Testing that involves the execution of the software of a component or system.

dynamic comparison

Comparison of actual andata expectedata results, performedata while the software is being executed, for example by a test execution tool.

dynamic analysis tool

A tool that provides run-time information on the state of the software code. These tools are most commonly usedatato identify unassignedatapointers, check pointer arithmetic andata to monitor the allocation, use andata de-allocation of memory andata to flag memory leaks.

dynamic analysis

The process of evaluating behavior, e.g. memory performance, CPU usage, of a system or component during execution. [After IEEE 610]

driver

A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system. [After TMap]

domain analysis

A black box test design technique that is usedata to identify efficient andata effective test cases when multiple variables can or shouldatabe testedatatogether. It builds on andatageneralizes equivalence partitioning andataboundary values analysis. See also boundary value analysis, equivalence partitioning.

domain

The set from which validatainput and/or output values can be selected.

documentation testing

Testing the quality of the documentation, e.g. user guide or installation guide.

dirty testing

See negative testing.

diagnosing (IDEAL)

The phase within the IDEAL model where it is determinedatawhere one is, relative to where one wants to be. The diagnosing phase consists of the activities characterize current andatadesiredatastates andatadevelop recommendations. See also IDEAL .

deviation report

See incident report.

deviation

See incident.

development testing

Formal or informal testing conductedataduring the implementation of a component or system, usually in the development environment by developers. [After IEEE 610]

desk checking

Testing of software or a specification by manual simulation of its execution. See also static testing.

design-basedatatesting

An approach to testing in which test cases are designedatabasedataon the architecture and/or detailedata design of a component or system (e.g. tests of interfaces between components or systems).

Deming cycle

An iterative four-step problem-solving process, (plan-do-check-act), typically usedatain process improvement. [After Deming]

deliverable

Any (work) product that must be deliveredata to someone other than the (work) product’s author.

definition-use pair

The association of a definition of a variable with the subsequent use of that variable. Variable uses include computational (e.g. multiplication) or to direct the execution of a path (“predicate” use).

defect type

An element in a taxonomy of defects. Defect taxonomies can be identifiedatawith respect to a variety of considerations, including, but not limitedatato • Phase or development activity in which the defect is created, e.g., a specification error or a coding error • Characterization of defects, e.g., an “off-by-one” defect • Incorrectness, e.g., an incorrect relational operator, a programming language syntax error, or an invalidataassumption • Performance issues, e.g., excessive execution time, insufficient availability.

defect triage committee

See defect management committee.