Istqb F.l. Glossary Chapter 6

Front 1

The effect on the component or system by the measurement instrument when the component or system is being measured, e.g. by a performance testing tool or monitor. For example performance may be slightly worse when performance testing tools are being used.

Back 1

Probe effect

Front 2

A tool that provides support to the test management and control part of a test process. It often has several capabilities, such as testware management, scheduling of tests, the logging of results, progress tracking, incident management and test reporting.

Back 2

Test management tool

Front 3

A tool that supports the recording of requirements, requirements attributes (e.g. priority, knowledge responsible) and annotation, and facilitates traceability through layers of requirements and requirements change management.

Back 3

Requirements management tool

Front 4

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

Back 4

Incident management tool (defect management tool)

Front 5

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.

Back 5

Configuration management tool

Front 6

A tool that provides support to the review process. Typical features include review planning and tracking support, communication support, collaborative reviews and a repository for collecting and reporting of metrics.

Back 6

Review tool

Front 7

Analysis of software artifacts, e.g. requirements or code, carried out without execution of these software development artifacts.

Back 7

Static analysis

Front 8

A tool that carries out static analysis.

Back 8

Static analysis tool (static analyzer)

Front 9

Analysis of source code carried out without execution of that software.

Back 9

Static code analysis

Front 10

A tool that carries out static code analysis. The tool checks source code, for certain properties such as conformance to coding standards, quality metrics or data flow anomalies.

Back 10

Static code analyzer

Front 11

A tool that supports the creation, amendment and verification of models of the software or system.

Back 11

Modeling tool

Front 12

A tool that supports the test design activity by generating test inputs from a specification that may be held in a CASE tool repository, e.g. requirements management tool, from specified test conditions held in the tool itself, or from code.

Back 12

Test design tool

Front 13

A type of test tool that enables data to be selected from existing databases or created, generated, manipulated and edited for use in testing.

Back 13

Test data preparation tool

Front 14

A type of test tool that is able to execute other software using an automated test script, e.g. capture/playback.

Back 14

Test execution tool

Front 15

A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.

Back 15

Capture/playback tool

Front 16

A test environment comprised of stubs and drivers needed to execute a test.

Back 16

Test harness

Front 17

A tool that provides an environment for unit or component testing in which a component can be tested in isolation or with suitable stubs and drivers. It also provides other support for the developer, such as debugging capabilities.

Back 17

Unit test framework tool

Front 18

A skeletal or special-purpose implementation of a software component, used to develop or test a component that calls or is otherwise dependent on it. It replaces a called component.

Back 18

Stub

Front 19

A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.

Back 19

Driver

Front 20

A test tool to perform automated test comparison of actual results with expected results.

Back 20

Test comparator

Front 21

The process of identifying differences between the actual results produced by the component or system under test and the expected results for a test.

Back 21

Test comparison

Front 22

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

Back 22

Coverage tool

Front 23

Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data.

Back 23

Security

Front 24

A tool that supports operational security.

Back 24

Security tool

Front 25

Testing to determine the security of the software product.

Back 25

Security testing

Front 26

A tool that provides support for testing security characteristics and vulnerabilities.

Back 26

Security testing tool

Front 27

A tool that provides run-time information on the state of the software code. These tools are most commonly used to identify unassigned pointers, check pointer arithmetic and to monitor the allocation, use and de-allocation of memory and to flag memory leaks.

Back 27

Dynamic analysis tool

Front 28

A tool that usually has two main facilities: load generation and test transaction measurement. Load generation can simulate either multiple users or high volumes of input data. During execution, response time measurements are taken from selected transactions and these are logged.

Back 28

Performance-testing tool (load-testing tool)

Front 29

A type of performance testing conducted to evaluate the behavior of a component or system with increasing ____.

Back 29

Load testing

Front 30

Testing where the system is subjected to large _______ of data.

Back 30

Volume testing

Front 31

A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified work loads, or with reduced availability of resources such as access to memory or servers.

Back 31

Stress testing

Front 32

A software tool or hardware device that runs concurrently with the component or system under test and supervises, records and/or analyses the behavior of the component or system.

Back 32

Monitor (monitoring tool)

Front 33

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

Back 33

Debugging

Front 34

A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect.

Back 34

Debugging tool

Front 35

A programming language in which executable test _______ are written, used by a test execution tool (e.g. a capture/playback tool).

Back 35

Scripting language

Front 36

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.

Back 36

Data-driven testing

Front 37

A scripting technique that uses data files to contain not only test data and expected results, but also ________ related to the application being tested.

Back 37

Keyword-driven testing.