Istqb Glossary Report - Foundation (V3.01) -- Part 10

Front 1

test process

Back 1

The fundamental __ comprises test planning and control, test analysis and design, test implementation and execution, evaluating exit criteria and reporting, and test closure activities.

Front 2

test process group (TPG)

Back 2

A collection of (test) specialists who facilitate the definition, maintenance, and improvement ofthe test processes used by an organization.

Front 3

test progress report

Back 3

A document summarizing testing activities and results, produced at regular intervals, to report progress of testing activities against a baseline (such as the original test plan) and to communicate risks and alternatives requiring a decision to management.

Front 4

test reporting

Back 4

Collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform stakeholders.

Front 5

test run

Back 5

Execution of a test on a specific version of the test object.

Front 6

test schedule

Back 6

A list of activities, tasks or events of the test process, identifying their intended start and finish dates and/or times, and interdependencies.

Front 7

test script

Back 7

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

Front 8

test session

Back 8

An uninterrupted period of time spent in executing tests. In exploratory testing, each __ is focused on a charter, but testers can also explore new opportunities or issues during a session. The tester creates and executes on the fly and records their progress.

Front 9

test specification

Back 9

A document that consists of a test design specification, test case specification and/or test procedure specification.

Front 10

test strategy

Back 10

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 11

test suite

Back 11

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.

Front 12

test summary report

Back 12

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

Front 13

test tool

Back 13

A software product that supports one or more test activities, such as planning and control, specification, building initial files and data, test execution and test analysis.

Front 14

test type

Back 14

A group of test activities aimed at testing a component or system focused on a specific test objective, i.e. functional test, usability test, regression test etc. It may take place on oneor more test levels or test phases.

Front 15

test-driven development (TDD)

Back 15

A way of developing software where the test cases are developed, and often automated, before the software is developed to run those test cases.

Front 16

testability

Back 16

The capability of the software product to enable modified software to be tested.

Front 17

tester

Back 17

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

Front 18

testing

Back 18

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 19

testware

Back 19

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 20

traceability

Back 20

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

Front 21

unit test framework

Back 21

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.

Front 22

dead code

Back 22

Code that cannot be reached and therefore is impossible to execute.

Front 23

usability

Back 23

The capability of the software to be understood, learned, used and attractive to the user when used under specified conditions.

Front 24

usability testing

Back 24

Testing to determine the extent to which the software product is understood, easy to learn, easy to operate and attractive to the users under specified conditions.

Front 25

use case

Back 25

A sequence of transactions in a dialogue between an actor and a component or system with a tangible result, where an actor can be a user or anything that can exchange information with the system.

Front 26

use case testing

Back 26

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

Front 27

user acceptance testing

Back 27

Acceptance testing carried out by future users in a (simulated) operational environment focusing on user requirements and needs.

Front 28

V-model

Back 28

A framework to describe the software development lifecycle activities from requirements specification to maintenance. The V-model illustrates how testing activities can be integrated into each phase of the software development lifecycle.

Front 29

validation

Back 29

Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.

Front 30

variable

Back 30

An element of storage in a computer that is accessible by a software program by referring to it by a name.

Front 31

verification

Back 31

Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.

Front 32

walkthrough

Back 32

A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content.

Front 33

white-box test design technique

Back 33

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

Front 34

white-box testing

Back 34

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