Istqb Glossary Report - Foundation (V3.01) -- Part 2

Front 1

condition coverage

Back 1

The percentage of condition outcomes that have been exercised by a test suite. 100% of it requires each single condition in every decision statement to be tested as True and False.

Front 2

configuration

Back 2

The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.

Front 3

version control

Back 3

An element of configuration management, consisting of the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items after formal establishment of their configuration identification.

Front 4

configuration item

Back 4

An aggregation of hardware, software or both, that is designated for configuration management and treated as a single entity in the configuration management process.

Front 5

configuration management

Back 5

A discipline applying technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements.

Front 6

configuration management tool

Back 6

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.

Front 7

re-testing

Back 7

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

Front 8

control flow

Back 8

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

Front 9

control flow testing

Back 9

An approach to structure-based testing in which test cases are designed to execute specific sequences of events. Various techniques exist for it, e.g., decision testing, condition testing, and path testing, that each have their specific approach and level of control flow coverage.

Front 10

conversion testing

Back 10

Testing of software used to convert data from existing systems for use in replacement systems.

Front 11

test coverage

Back 11

The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test suite.

Front 12

coverage tool

Back 12

A tool that provides objective measures of what structural elements, e.g., statements, branches have been exercised by a test suite.

Front 13

data flow

Back 13

An abstract representation of the sequence and possible changes of the state of data objects, where the state of an object is any of creation, usage, or destruction.

Front 14

data quality

Back 14

An attribute of data that indicates correctness with respect to some pre-defined criteria, e.g., business expectations, requirements on data integrity, data consistency.

Front 15

data-driven testing

Back 15

A scripting technique that stores test input and expected results in a table or spreadsheet, so that a single control script can execute all of the tests in the table. It is often used to support the application of test execution tools such as capture/playback tools.

Front 16

debugging

Back 16

The process of finding, analyzing and removing the causes of failures in software.

Front 17

debugging tool

Back 17

A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. These tools enable programmers to execute programs step by step, to halt a program at any program statement and to set and examine program variables.

Front 18

decision

Back 18

A program point at which the control flow has two or more alternative routes. A node with two or more links to separate branches.

Front 19

decision coverage

Back 19

The percentage of decision outcomes that have been exercised by a test suite. 100% of it implies both 100% branch coverage and 100% statement coverage.

Front 20

decision outcome

Back 20

The result of a decision (which therefore determines the branches to be taken).

Front 21

decision table

Back 21

A table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects), which can be used to design test cases.

Front 22

decision table testing

Back 22

A black-box test design technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table.

Front 23

decision testing

Back 23

A white-box test design technique in which test cases are designed to execute decision outcomes.

Front 24

defect / bug / fault

Back 24

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. If encountered during execution, it may cause a failure of the component or system.

Front 25

defect density

Back 25

The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g., lines-of-code, number of classes or function points).

Front 26

defect tracking tool / bug tracking tool

Back 26

A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities.

Front 27

defect type

Back 27

An element in a taxonomy of defects. Defect taxonomies can be identified with respect to a variety of considerations, including, but not limited to: 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 invalid assumption, Performance issues, e.g., excessive execution time, insufficient availability.

Front 28

deliverable

Back 28

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

Front 29

development testing

Back 29

Formal or informal testing conducted during the implementation of a component or system, usually in the development environment by developers.

Front 30

domain

Back 30

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