Istqb F.l. Glossary Chapter 1

Front 1

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.

Back 1

Requirement

Front 2

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

Back 2

Debugging

Front 3

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

Back 3

Test Case

Front 4

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

Back 4

Review

Front 5

A reason or purpose for designing and executing a test.

Back 5

Test Objective

Front 6

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

Back 6

Bug - Defect - Fault

Front 7

A human action that produces an incorrect result.

Back 7

Error - Mistake

Front 8

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

Back 8

Failure

Front 9

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

Back 9

Quality

Front 10

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

Back 10

Risk

Front 11

The process consisting of all life cycle 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.

Back 11

Testing

Front 12

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

Back 12

Exhaustive Testing

Front 13

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

Back 13

Exit Criteria

Front 14

Any event occurring that requires investigation.

Back 14

Incident

Front 15

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.

Back 15

Regression Testing

Front 16

All documents from which the requirements of a component or system can be inferred.

Back 16

Test Basis

Front 17

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

Back 17

Test Condition

Front 18

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

Back 18

Coverage - Test Coverage

Front 19

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.

Back 19

Test Data

Front 20

The process of running a test on the component or system under test, producing actual results.

Back 20

Test Execution

Front 21

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

Back 21

Test Log

Front 22

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

Back 22

Test Policy

Front 23

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 23

Test Strategy

Front 24

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 24

Test Control

Front 25

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 25

Test Monitoring

Front 26

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

Back 26

Test Case

Front 27

A document specifying the test conditions (coverage items) for a test item, the detailed test approach and the associated high-level test cases.

Back 27

Test Design Specification

Front 28

A document specifying a sequence of actions for the execution of a test.

Back 28

Test Procedure Specification

Front 29

A set of several test cases for a component or system under test, where the postcondition of one test is often used as the precondition for the next one.

Back 29

Test Suite

Front 30

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

Back 30

Retesting - Confirmation Testing

Front 31

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

Back 31

Test Summary Report

Front 32

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

Back 32

Testware

Front 33

Separation of responsibilities, which encourages the accomplishment of objective testing.

Back 33

Independence

Front 34

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.

Back 34

Error Guessing