Istqb F.l. Glossary Chapter 5

Front 1

A skilled professional who is involved in the testing of a component or system.

Back 1

Tester

Front 2

The person responsible for project management of testing activities and resources, and evaluation of a test object. The individual who directs, controls, administers, plans and regulates the evaluation of a test object.

Back 2

Test manager (test leader)

Front 3

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, and the rationale for their choice, and any risks requiring contingency planning.

Back 3

Test plan

Front 4

A group of test activities that are organized and managed together.

Back 4

Test level

Front 5

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

Back 5

Entry criteria

Front 6

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

Back 6

Exit criteria

Front 7

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

Back 7

Test strategy

Front 8

The implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) project’s goal and the risk assessment carried out, starting points regarding the test process, the test design techniques to be applied, exit criteria and test types to be performed.

Back 8

Test approach

Front 9

A test management task that deals with the activities related to periodically checking the status of a test project. Reports are prepared that compare the actuals to that which was planned.

Back 9

Test monitoring

Front 10

The planning, estimating, monitoring and control of test activities.

Back 10

Test management

Front 11

The ratio of the number of failures of a given category to a given unit of measure, e.g. failures per unit of time, failures per number of transactions, failures per number of computer runs.

Back 11

Failure rate

Front 12

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).

Back 12

Defect density

Front 13

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

Back 13

Test summary report (test report)

Front 14

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.

Back 14

Test control

Front 15

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.

Back 15

Configuration management

Front 16

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

Back 16

Configuration control (version control)

Front 17

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

Back 17

Risk

Front 18

A risk directly related to the test object.

Back 18

Product risk

Front 19

An approach to testing to reduce the level of product risks and inform stakeholders on their status, starting in the initial stages of a project. It involves the identification of product risks and their use in guiding the test process.

Back 19

Risk-based testing

Front 20

A risk related to management and control of the (test) project, e.g. lack of staffing, strict deadlines, changing requirements, etc.

Back 20

Project risk

Front 21

A source of a defect such that if it is removed, the occurance of the defect type is decreased or removed.

Back 21

Root cause

Front 22

Recording the details of any incident that occurred, e.g. during testing.

Back 22

Incident logging

Front 23

A document reporting on any event that occurred, e.g. during the testing, which requires investigation.

Back 23

Incident report

Front 24

A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function.

Back 24

Defect report (bug report)

Front 25

The number of defects found by a test phase, divided by the number found by that test phase and any other means afterwards.

Back 25

Defect detection percentage (DDP)

Front 26

The level of (business) importance assigned to an item, e.g. defect.

Back 26

Priority

Front 27

The degree of impact that a defect has on the development or operation of a component or system.

Back 27

Severity