Istqb Glossary Terms

Front 1

test case:

Back 1

A set of input values, execution preconditions, expected results and execution post conditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement.

Front 2

test casespecification

Back 2

A document specifying a set of test cases (objective, inputs, test actions, expected results, and execution preconditions) for a test item.

Front 3

test condition:

Back 3

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

Front 4

equivalencepartition:

Back 4

A portion of an input or output domain for which the behavior of a component or system is assumed to be the same, based on the specification

Front 5

specification-based testing:

Back 5

See black box testing.

Front 6

state transitiontesting:

Back 6

A black box test design technique in which test cases are designed to execute valid and invalid state transitions.

Front 7

exploratorytesting:

Back 7

An informal test design technique where the tester actively controls the ATA design of the tests as those tests are performed and uses information gained while testing to design new and better tests

Front 8

back-to-backtesting:

Back 8

Testing in which two or more variants of a component or system are executed with the same inputs, the outputs compared, and analyzed in cases of discrepancies

Front 9

trace ability:

Back 9

The ability to identify related items in documentation and software, such as requirements with associated tests

Front 10

test script:

Back 10

Commonly used to refer to a test procedure specification, especially an automated one

Front 11

test procedurespecification:

Back 11

A document specifying a sequence of actions for the execution ATM of a test. Also known as test script or manual test script. n;margin-bottom

Front 12

test data:

Back 12

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

Front 13

decision tabletesting:

Back 13

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 14

boundary valueanalysis:

Back 14

A black box test design technique in which test cases are designed based on boundary values

Front 15

white-box test design technique:

Back 15

Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system.

Front 16

statement coverage:

Back 16

The percentage of executable statements that have been exercised by test suite

Front 17

decision coverage:

Back 17

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

Front 18

code coverage:

Back 18

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.

Front 19

use case testing:

Back 19

A black box test design technique in which test cases are designed to execute scenarios of use cases.

Front 20

error guessing:

Back 20

A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made, and to design tests specifically to expose them.

Front 21

structure-based test design technique: is the same as

structural testing, testing structure-based testing/ See white-box testing.

Back 21

See white-box

Front 22

white-box testing:

Back 22

Testing based on an analysis of the internal structure of the component or system.

Front 23

exploratorytesting:

Back 23

An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests.

Front 24

black box testing

Back 24

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

Front 25

black box technique:

Back 25

See black box test design technique