Istqb - Chapter 1: Glossary Terms

Front 1

Defect (bug, fault)

Back 1

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.

Front 2

Error (mistake)

Back 2

A human action that produces an incorrect result.

Front 3

Failure

Back 3

Deviation of the component or system from its expected delivery, service or result.

Front 4

Quality

Back 4

The degree to which a component, system or process meets specified requirements
and/or user/customer needs and expectations. [After IEEE 610]

Front 5

Risk

Back 5

A factor that could result in future negative consequences; usually expressed as impact
and likelihood.

Front 6

Software

Back 6

Computer programs, procedures, and possibly associated documentation and data
pertaining to the operation of a computer system. [IEEE 610]

Front 7

Testing

Back 7

The process consisting of all lifecycle activities, both static and dynamic, concerned
with planning, preparation and evaluation of software products and related work products
to determine that they satisfy specified requirements, to demonstrate that they are fit for
purpose and to detect defects.

Front 8

Testware

Back 8

Artifacts produced during the test process required to plan, design, and execute
tests, such as documentation, scripts, inputs, expected results, set-up and clear-up
procedures, files, databases, environment, and any additional software or utilities used in
testing.

Front 9

Exhaustive (complete) testing

Back 9

A test approach in which the test suite comprises all combinations of
input values and preconditions

Front 10

Re-testing

Back 10

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

Front 11

Regression testing

Back 11

Testing of a previously tested program following modification to ensure
that defects have not been introduced or uncovered in unchanged areas of the software, as a
result of the changes made. It is performed when the software or its environment is
changed.

Front 12

Debugging

Back 12

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

Front 13

Requirement

Back 13

A condition or capability needed by a user to solve a problem or achieve an
objective that must be met or possessed by a system or system component to satisfy a
contract, standard, specification, or other formally imposed document. [After IEEE 610]

Front 14

Review

Back 14

An evaluation of a product or project status to ascertain discrepancies from planned
results and to recommend improvements.

Front 15

Test basis

Back 15

All documents from which the requirements of a component or system can be
inferred. The documentation on which the test cases are based.

Front 16

Test case

Back 16

A set of input values, execution preconditions, expected results and execution
postconditions, developed for a particular objective or test condition

Front 17

Confirmation testing

Back 17

is a synonim of re-testing

Front 18

Exit criteria

Back 18

The set of generic and specific conditions, agreed upon with the stakeholders,
for permitting a process to be officially completed.

Front 19

Entry criteria

Back 19

The set of generic and specific conditions for permitting a process to go
forward with a defined task, e.g. test phase.

Front 20

Incident

Back 20

Any event occurring that requires investigation

Front 21

Test condition

Back 21

An item or event of a component or system that could be verified by one or
more test cases

Front 22

Test coverage (coverage)

Back 22

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

Front 23

Test data

Back 23

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 24

Test execution

Back 24

The process of running a test on the component or system under test,
producing actual result(s).

Front 25

Test log

Back 25

A chronological record of relevant details about the execution of tests.

Front 26

Test plan

Back 26

A document describing the scope, approach, resources and schedule of intended
test activities. It identifies amongst others test items, the features to be tested, the testing
tasks, who will do each task, degree of tester independence, the test environment, the test
design techniques and entry and exit criteria to be used

Front 27

Test strategy

Back 27

A high-level description of the test levels to be performed and the testing within
those levels for an organization or programme (one or more projects).

Front 28

Test policy

Back 28

A high level document describing the principles, approach and major objectives
of the organization regarding testing.

Front 29

Test summary report

Back 29

A document summarizing testing activities and results. It also contains
an evaluation of the corresponding test items against exit criteria.

Front 30

Test control

Back 30

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.

Front 31

Testability

Back 31

The capability of the software product to enable modified software to be tested.
[ISO 9126]