Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

ISTQB Glossary > Part 1 > Flashcards

Part 1 Flashcards

1
Q

The degree to which a component or system
provides functions that meet stated and implied
needs when used under specified conditions.

A

functional suitability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

The degree to which a component or system uses
time, resources and capacity when accomplishing
its designated functions.

A

performance

efficiency

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

A review technique carried out by independent reviewers informally,
without a structured process.

A

ad hoc reviewing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

A review technique guided by a list of questions or required attributes.

A

checklist-based

reviewing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

decision table in which combinations of inputs that are impossible or
lead to the same outputs are merged into one column (rule), by setting
the conditions that do not influence the outputs to don’t care.

A

collapsed decision table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

The degree to which a component or system can exchange information
with other components or systems.

A

compatibility

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Acceptance testing conducted to verify whether a system satisfies its
contractual requirements

A

contractual

acceptance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

The leader and main person responsible for an inspection or review
process.

A

facilitator

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

An informal review performed by three or more persons.

A

informal group

review

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

A test tool that generates load for a designated test item and that
measures and records its performance during test execution.

A

performance

testing tool

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

A review technique whereby reviewers evaluate the work product
from different viewpoints

A

perspective-based

reading

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

An unknown underlying cause of one or more incidents.

A

problem

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

A degradation in the quality of a component or system due to a
change

A

regression

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Acceptance testing conducted to verify whether a system conforms to
relevant laws, policies and regulations.

A

regulatory

acceptance testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

A review technique where reviewers evaluate a work product from the
perspective of different stakeholder roles.

A

role-based

reviewing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

A review technique where the review is guided by determining the
ability of the work product to address specific scenarios

A

scenario-based

reviewing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

A type of development lifecycle model in which a complete system is
developed in a linear way of several discrete and successive phases
with no overlap between them

A

sequential
development
model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

The activities performed at each stage in software development, and
how they relate to one another logically and chronologically

A

software
development
lifecycle

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

The activity that makes test assets available for later use, leaves test
environments in a satisfactory condition and communicates the results
of testing to relevant stakeholders

A

Test completion

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

A test tool that executes tests against a designated test item and
evaluates the outcomes against expected results and postconditions

A

Test execution tool

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

The practice of designing tests based on the specification of a test item
before developing the corresponding test item

A

test-first

development

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

On large projects, the person who reports to the test manager and is
responsible for project management of a particular test level or a
particular set of testing activities

A

test leader

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

A sequence of test cases in execution order, and any associated actions
that may be required to set up the initial preconditions and any wrap
up activities post execution.

A

test procedure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Documentation summarizing test activities and results

A

test report

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

A procedure to derive and/or select test cases
based on an analysis of the specification, either
functional or non-functional, of a component or
system without reference to its internal structure

A

black-box test

technique

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

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

A

defect detection

percentage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

A procedure to derive and/or select test cases
based on the tester’s experience, knowledge and
intuition.

A

experience-based

test technique

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

A category of product attributes that bears on

quality

A

quality characteristic

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

A procedure used to derive and/or select test

cases

A

test technique

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

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

A

white-box test

technique

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

The criteria that a component or system must satisfy in order to be
accepted by a user, customer, or other authorized entity.

A

acceptance

criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

The degree to which a component or system can be used by people
with the widest range of characteristics and capabilities to achieve a
specified goal in a specified context of use.

A

accessibility

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

The degree to which a component or system can be adapted for
different or evolving hardware and software environments.

A

adaptability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

Simulated or actual operational testing conducted in the
developer’s test environment, by roles outside the development
organization

A

alpha testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

The degree to which an assessment can be made for a component
or system of either the impact of one or more intended changes,
the diagnosis of deficiencies or causes of failures, or the
identification of parts to be modified.

A

analyzability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

An independent examination of a work product, process, or set of
processes that is performed by a third party to assess compliance
with specifications, standards, contractual agreements, or other
criteria.

A

audit

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

Simulated or actual operational testing conducted at an external
site, by roles outside the development organization.

A

beta testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

An integration test approach in which software elements, hardware
elements, or both are combined all at once into a component or an
overall system, rather than in stages.

A

big-bang testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

A minimum or maximum value of an ordered equivalence partition.

A

boundary value

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

A black-box test technique in which test cases are designed based
on boundary values.

A

boundary value

analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

The coverage of boundary values

A

boundary value

coverage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
42
Q

A transfer of control from one location to a different location in the
code.

A

branch

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
43
Q

The coverage of branches.

A

branch coverage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
44
Q

An experience-based test technique whereby the experienced
tester uses a high-level list of items to be noted, checked, or
remembered, or a set of rules or criteria against which a product
has to be verified.

A

checklist-based

testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
45
Q

The degree to which a component or system can perform its
required functions while sharing an environment and resources
with other components or systems without a negative impact on
any of them.

A

co-existence

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
46
Q

A computer program that translates programs expressed in a high- order language into their machine language equivalents

A

compiler

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
47
Q

A minimal part of a system that can be tested in isolation.

A

component

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
48
Q

The testing of individual hardware or software components

A

component

testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q

An aggregation of work products that is designated for
configuration management and treated as a single entity in the
configuration management process.

A

configuration item

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
50
Q

Dynamic testing conducted after fixing defects with the objective to
confirm that failures caused by those defects do not occur anymore.

A

confirmation

testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
51
Q

The sequence in which operations are performed during the

execution of a test item.

A

control flow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
52
Q

A form of static analysis based on a control flow graph.

A

control flow

analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
53
Q

An abstract representation of all possible control flows through a
component or system.

A

Control flow graph

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
54
Q

A test technique in which test cases are designed on the basis of
control flows.

A

control flow

testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
55
Q

The degree to which specified coverage items have been
determined or have been exercised by a test suite expressed as a
percentage.

A

coverage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
56
Q

An attribute or combination of attributes that is derived from one
or more test conditions by using a test technique that enables the
measurement of the thoroughness of the test execution.

A

coverage item

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
57
Q

The maximum number of linear, independent paths through a
program. Cyclomatic complexity may be computed as L - N + 2P,
where L = the number of edges/links in a graph, N = the number of
nodes in a graph, P = the number of disconnected parts of the graph
(e.g., a called graph or subroutine).

A

cyclomatic

complexity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
58
Q

A type of statement in which a choice between two or more

possible outcomes controls which set of actions will result.

A

decision

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
59
Q

The coverage of decision outcomes.

A

decision coverage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
60
Q

The result of a decision that determines the next statement to be
executed.

A

decision outcome

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
61
Q

A table used to show sets of conditions and the actions resulting
from them.

A

decision table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
62
Q

A black-box test technique in which test cases are designed to
execute the combinations of inputs and/or stimuli (causes) shown in
a decision table.

A

decision table

testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
63
Q

A white-box test technique in which test cases are designed to
execute decision outcomes.

A

decision testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
64
Q

An imperfection or deficiency in a work product where it does not
meet its requirements or specifications.

A

defect

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
65
Q

The number of defects per unit size of a work product.

A

defect density

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
66
Q

The process of recognizing and recording defects, classifying them,
investigating them, taking action to resolve them, and disposing of
them when resolved.

A

defect

management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
67
Q

A tool that facilitates the recording and status tracking of defects.

A

defect

management tool

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
68
Q

Documentation of the occurrence, nature, and status of a defect.

A

defect report

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
69
Q

The set of conditions for officially starting a defined task.

A

entry criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
70
Q

A portion of the value domain of a data element related to the test
object for which all values are expected to be treated the same
based on the specification.

A

equivalence

partition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
71
Q

A black-box test technique in which test cases are designed to
exercise equivalence partitions by using one representative
member of each partition.

A

equivalence

partitioning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
72
Q

A test technique in which tests are derived on the basis of the
tester’s knowledge of past failures, or general knowledge of failure
modes.

A

error guessing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
73
Q

A defect that was not detected in a previous test level which is
supposed to find such type of defects.

A

escaped defect

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
74
Q

The set of conditions for officially completing a defined task.

A

exit criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
75
Q

The predicted observable behavior of a component or system
executing under specified conditions, based on its specification or
another source.

A

expected result

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
76
Q

An approach to testing whereby the testers dynamically design and
execute tests based on their knowledge, exploration of the test
item and the results of previous tests.

A

exploratory

testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
77
Q

An event in which a component or system does not perform a

required function within specified limits.

A

failure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
78
Q

The ratio of the number of failures of a given category to a given
unit of measure.

A

failure rate

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
79
Q

A form of review that follows a defined process with a formally
documented output.

A

formal review

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
80
Q

A requirement that specifies a function that a component or system
must be able to perform.

A

functional

requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
81
Q

Testing conducted to evaluate the compliance of a component or
system with functional requirements.

A

functional testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
82
Q

A test case without concrete values for input data and expected
results.

A

high-level test
case
Synonyms: abstract test case , logical test case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
83
Q

The identification of all work products affected by a change,
including an estimate of the resources needed to accomplish the
change.

A

impact analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
84
Q

An event occurring that requires investigation.

A

incident

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
85
Q

The process of recognizing and recording incidents, classifying
them, investigating them, taking action to resolve them, and
disposing of them when resolved.

A

incident

management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
86
Q

A tool that facilitates the recording and status tracking of incidents.

A

incident

management tool

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
87
Q

Documentation of the occurrence, nature, and status of an incident.

A

incident report

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
88
Q

A development lifecycle model in which the project scope is
generally determined early in the project lifecycle, but time and
cost estimates are routinely modified as the project team
understanding of the product increases. The product is developed
through a series of repeated cycles, each delivering an increment
which successively adds to the functionality of the product.

A

incremental
development
model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
89
Q

A measure that provides an estimate or evaluation of specified
attributes derived from a model with respect to defined information
needs.

A

indicator

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
90
Q

A type of review without a formal (documented) procedure.

A

informal review

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
91
Q

Data received by a component or system from an external source.

A

input

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
92
Q

A type of formal review to identify issues in a work product, which
provides measurement to improve the review process and the
software development process.

A

inspection

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
93
Q

The degree to which two or more components or systems can
exchange information and use the information that has been
exchanged.

A

interoperability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
94
Q

A description of the processes, workflows, and activities used in the
development, delivery, maintenance, and retirement of a system.

A

lifecycle model

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
95
Q

A type of performance testing conducted to evaluate the behavior
of a component or system under varying loads, usually between
anticipated conditions of low, typical, and peak usage.

A

load testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
96
Q

A test case with concrete values for input data and expected results.

A

low-level test case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
97
Q

The degree to which a component or system can be modified by the
intended maintainers.

A

maintainability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
98
Q

The process of modifying a component or system after delivery to
correct defects, improve quality attributes, or adapt to a changed
environment.

A

maintenance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
99
Q

A test plan that is used to coordinate multiple test levels or test
types.

A

master test plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
100
Q

(1) The capability of an organization with respect to the
effectiveness and efficiency of its processes and work practices.
(2) The degree to which a component or system meets needs for
reliability under normal operation.

A

maturity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
101
Q

The coverage of model elements

A

model coverage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
102
Q

A neutral person who conducts a usability test session.

A

moderator

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
103
Q

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

A

monitoring tool

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
104
Q

A requirement that describes how the component or system will do
what it is intended to do.

A

non-functional

requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
105
Q

Testing conducted to evaluate the compliance of a component or
system with non-functional requirements.

A

non-functional

testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
106
Q

Model-based test approach whereby test cases are generated into a
repository for future execution.

A

offline MBT

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
107
Q

Model-based test approach whereby test cases are generated and
executed simultaneously.

A

online MBT

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
108
Q

An actual or predicted pattern of use of the component or system.

A

operational profile

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
109
Q

Data transmitted by a component or system to an external

destination.

A

output

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
110
Q

An agile software development practice in which two programmers
work together on one workstation.

A

pair programming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
111
Q

The coverage of paths

A

path coverage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
112
Q

A form of review of work products performed by others qualified to
do the same work.

A

peer review

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
113
Q

The expected state of a test item and its environment at the end of
test case execution.

A

postcondition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
114
Q

The required state of a test item and its environment prior to test
case execution.

A

precondition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
115
Q

A risk impacting the quality of a product.

A

product risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
116
Q

A view of quality, wherein quality is based on a well-defined set of
quality characteristics. These characteristics must be measured in
an objective and quantitative way. Differences in the quality of
products of the same type can be traced back to the way the
specific quality characteristics have been implemented.

A

product-based

quality

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
117
Q

A risk that impacts project success.

A

project risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
118
Q

A product risk related to a quality characteristic.

A

quality risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
119
Q

Testing of a previously tested component or system following
modification to ensure that defects have not been introduced or
have been uncovered in unchanged areas of the software, as a
result of the changes made.

A

regression testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
120
Q

The degree to which a component or system performs specified
functions under specified conditions for a specified period of time.

A

reliability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
121
Q

A provision that contains criteria to be fulfilled.

A

requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
122
Q

The period of time in the software lifecycle during which the
requirements for a software product are defined and documented.

A

requirements

phase

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
123
Q

A type of static testing during which a work product or process is
evaluated by one or more individuals to detect issues and to
provide improvements.

A

review

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
124
Q

A participant in a review, who identifies issues in the work product.

A

reviewer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
125
Q

The overall process of risk identification and risk assessment.

A

risk analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
126
Q

The process to examine identified risks and determine the risk level.

A

risk assessment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
127
Q

The process of finding, recognizing and describing risks.

A

risk identification

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
128
Q

The qualitative or quantitative measure of a risk defined by impact
and likelihood.

A

risk level

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
129
Q

The coordinated activities to direct and control an organization with
regard to risk.

A

risk management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
130
Q

The process through which decisions are reached and protective
measures are implemented for reducing or maintaining risks to
specified levels.

A

risk mitigation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
131
Q

A set of risks grouped by one or more common factors.

A

risk type

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
132
Q

Testing in which the management, selection, prioritization, and use
of testing activities and resources are based on corresponding risk
types and risk levels.

A

risk-based testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
133
Q

The capability that a system will not, under defined conditions, lead
to a state in which human life, health, property, or the environment
is endangered.

A

safety

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
134
Q

A person who records information during the review meetings.

A

scribe

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
135
Q

The degree to which a component or system protects information
and data so that persons or other components or systems have the
degree of access appropriate to their types and levels of
authorization.

A

security

136
Q

The degree to which a component or system can be effectively and
efficiently modified without introducing defects or degrading
existing product quality.

A

stability

137
Q

A black-box test technique using a state transition diagram or state
table to derive test cases to evaluate whether the test item
successfully executes valid transitions and blocks invalid transitions.

A

state transition

testing

138
Q

A white-box test technique in which test cases are designed to
execute statements.

A

statement testing

139
Q

The process of evaluating a component or system without executing
it, based on its form, structure, content, or documentation.

A

static analysis

140
Q

Testing a work product without code being executed.

A

static testing

141
Q

A collection of interacting elements organized to accomplish a
specific function or set of functions.

A

system

142
Q

Testing the combination and interaction of systems.

A

System
Integration
Testing

143
Q

A type of test object that is a system

A

system under test

144
Q

A structured testing methodology also used as a content-based
model for improving the testing process. It does not require that
improvements occur in a specific order.

A

Systematic Test
and Evaluation
Process

145
Q

A formal review type by a team of technically-qualified personnel
that examines the suitability of a work product for its intended use
and identifies discrepancies from specifications and standards.

A

technical review

146
Q

The activity that identifies test conditions by analyzing the test
basis.

A

test analysis

147
Q

The implementation of the test strategy for a specific project.

A

test approach

148
Q

The body of knowledge used as the basis for test analysis and
design.

A

test basis

149
Q

A set of preconditions, inputs, actions (where applicable), expected
results and postconditions, developed based on test conditions.

A

test case

150
Q

Documentation of a set of one or more test cases

A

test case

specification

151
Q

Documentation of test activities in session-based exploratory
testing.

A

test charter

152
Q

An aspect of the test basis that is relevant in order to achieve
specific test objectives.

A

test condition

153
Q

Data created or selected to satisfy the execution preconditions and
inputs to execute one or more test cases.

A

test data

154
Q

The activity of deriving and specifying test cases from test
conditions.

A

test design

155
Q

Documentation specifying the features to be tested and their
corresponding test conditions.

A

test design

specification

156
Q

A schedule for the execution of test suites within a test cycle.

A

test execution

schedule

157
Q

The activity that prepares the testware needed for test execution
based on test analysis and design.

A

test

implementation

158
Q

A part of a test object used in the test process.

A

test item

159
Q

A specific instantiation of a test process.

A

test level

160
Q

The activity of creating a test log.

A

test logging

161
Q

The planning, scheduling, estimating, monitoring, reporting, control
and completion of test activities.

A

test management

162
Q

A test management activity that involves checking the status of
testing activities, identifying any variances from the planned or
expected status, and reporting status to stakeholders.

A

test monitoring

163
Q

A source to determine expected results to compare with the actual
result of the system under test.

A

test oracle

164
Q

Documentation describing the test objectives to be achieved and
the means and the schedule for achieving them, organized to
coordinate testing activities.

A

test plan

165
Q

Documentation specifying one or more test procedures

A

test procedure

specification

166
Q

The set of interrelated activities comprising of test planning, test
monitoring and control, test analysis, test design, test
implementation, test execution, and test completion

A

test process

167
Q

A test report produced at regular intervals about the progress of
test activities against a baseline, risks, and alternatives requiring a
decision.

A

test progress

report

168
Q

A sequence of instructions for the execution of a test.

A

test script

169
Q

The complete documentation of the test design, test cases and test
procedures for a specific test item.

A

test specification

170
Q

Documentation that expresses the generic requirements for testing
one or more projects run within an organization, providing detail on
how testing is to be performed, and is aligned with the test policy.

A

test strategy

171
Q

A set of test cases or test procedures to be executed in a specific
test cycle.

A

test suite

172
Q

A test report that provides an evaluation of the corresponding test
items against exit criteria.

A

test summary

report

173
Q

A group of test activities based on specific test objectives aimed at
specific characteristics of a component or system.

A

test type

174
Q

The degree of effectiveness and efficiency with which tests can be
designed and executed for a component or system.

A

testability

175
Q

A review to evaluate the testability of the test basis.

A

testability review

176
Q

Work products produced during the test process for use in planning,
designing, executing, evaluating and reporting on testing.

A

testware

177
Q

The degree to which a relationship can be established between two
or more work products.

A

traceability

178
Q

The degree to which a component or system can be used by
specified users to achieve specified goals in a specified context of
use.

A

usability

179
Q

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

A

use case testing

180
Q

Acceptance testing conducted in a real or simulated operational
environment by intended users focusing their needs, requirements
and business processes.

A

user acceptance

testing

181
Q

A sequential development lifecycle model describing a one-for-one
relationship between major phases of software development from
business requirements specification to delivery, and corresponding
test levels from acceptance testing to component testing.

A

V-model

182
Q

A type of review in which an author leads members of the review
through a work product and the members ask questions and make
comments about possible issues.

A

walkthrough

183
Q

Deliverable oriented hierarchical decomposition of the work to be
executed by the project team to accomplish the project objectives
(according to PMBOK).

A

work breakdown

structure

184
Q

Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to
enable the user, customers or other authorized entity to determine whether or not to accept the system.

A

acceptance testing

185
Q

Testing to determine the ease by which users with disabilities can use a component or system.

A

accessibility testing

186
Q

The behavior produced/observed when a component or system is tested.

A

actual result

187
Q

Any condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, etc., or from someone’s perception or
experience. Anomalies may be found during, but not limited to, reviewing, testing, analysis, compilation, or use of software products or applicable documentation.

A

anomaly

188
Q

The degree to which a component or system is operational and accessible when required for use.

A

availability

189
Q

The response of a component or system to a set of input values and preconditions.

A

behavior

190
Q

A procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system without reference to its
internal structure.

A

black-box test technique

191
Q

A publicly displayed chart that depicts the outstanding effort versus time in an iteration. It shows the status and trend of completing the tasks of the iteration. The X-axis typically
represents days in the sprint, while the Y-axis is the remaining effort (usually either in ideal engineering hours or story points).

A

burndown chart

192
Q

An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g., statement
coverage, decision coverage or condition

A

code coverage

193
Q

A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.

A

commercial off-the-shelf (COTS)

Synonyms: off-the-shelf software

194
Q

The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.

A

complexity

195
Q

The capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions.

A

compliance

196
Q

A minimal part of a system that can be tested in isolation.

A

Component

197
Q

Testing performed to expose defects in the interfaces and interactions between integrated components.

A

component integration testing

Synonyms: link testing

198
Q

A description of a component’s function in terms of its output values for specified input values under specified conditions, and required non-functional behavior (e.g., resourceutilization).

A

component specification

199
Q

A logical expression that can be evaluated as True or False, e.g., A>B.

A

condition
See Also: condition testing
Synonyms: branch condition

200
Q

The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.

A

configuration

201
Q

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.

A

configuration management

202
Q

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.

A

configuration management tool

203
Q

The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal failure costs and external failure costs.

A

cost of quality

204
Q

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

A

coverage tool

205
Q

An abstract representation of the sequence and possible changes of the state of data objects, where the state of an object is any of creation, usage, or destruction.

A

data flow

206
Q

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. Data-driven
testing is often used to support the application of test execution tools such as capture/playback tools.

A

data-driven testing

207
Q

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

A

debugging

208
Q

A type of statement in which a choice between two or more possible outcomes controls which set of actions will result.

A

decision

209
Q

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.

A

driver

Synonyms: test driver

210
Q

The process of evaluating behavior, e.g., memory performance, CPU usage, of a system or component during execution.

A

dynamic analysis

211
Q

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.

A

dynamic analysis tool

212
Q

Testing that involves the execution of the software of a component or system.

A

dynamic testing

213
Q

Extent to which correct and complete goals are achieved.

A

effectiveness

214
Q

Resources expended in relation to the extent with which users achieve specified goals.

A

efficiency

215
Q

A human action that produces an incorrect result

A

error

216
Q

A statement which, when compiled, is translated into object code, and which will be executed procedurally when the program is running and may perform an action on data.

A

executable statement

217
Q

A program element is said to be exercised by a test case when the input value causes the execution of that element, such as a statement, decision, or other structural element.

A

exercised

218
Q

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

A

exhaustive testing

Synonyms: complete testing

219
Q

Testing based on the tester’s experience, knowledge and intuition.

A

experience-based testing

220
Q

A software engineering methodology used within Agile software development whereby core practices are programming in pairs, doing extensive code review, unit testing of all
code, and simplicity and clarity in code.

A

Extreme Programming (XP)

221
Q

A test is deemed to fail if its actual result does not match its expected result.

A

fail

222
Q

An attribute of a component or system specified or implied by requirements documentation (for example reliability, usability or design constraints).

A

feature

Synonyms: software feature

223
Q

A result of an evaluation that identifies some important issue, problem, or opportunity.

A

finding

224
Q

An integration approach that combines the components or systems for the purpose of getting a basic functionality working early.

A

functional integration

See Also: integration testing

225
Q

Acronym for Graphical User Interface.

A

GUI

226
Q

An organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions. The IDEAL model is named for the five phases
it describes: initiating, diagnosing, establishing, acting, and learning.

A

IDEAL

227
Q

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

A

independence of testing

228
Q

Supplied instructions on any suitable media, which guides the installer through the installation process. This may be a manual guide, step-by-step procedure, installation
wizard, or any other similar process description.

A

installation guide

229
Q

The process of combining components or systems into larger assemblies.

A

integration

230
Q

Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.

A

integration testing

231
Q

Testing to determine the interoperability of a software product.

A

interoperability testing
See Also: functionality testing
Synonyms: compatibility testing

232
Q

A development lifecycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or
external) of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product.

A

iterative development model

233
Q

A scripting technique that uses data files to contain not only test data and expected results, but also keywords related to the application being tested. The keywords are
interpreted by special supporting scripts that are called by the control script for the test.

A

keyword-driven testing
See Also: data-driven testing
Synonyms: action word-driven testing

234
Q

Testing the changes to an operational system or the impact of a changed environment to an operational system.

A

maintenance testing

235
Q

The number or category assigned to an attribute of an entity by making a measurement.

A

measure

236
Q

The process of assigning a number or category to an entity to describe an attribute of that entity.

A

measurement

237
Q

A memory access failure due to a defect in a program’s dynamic store allocation logic that causes it to fail to release memory after it has finished using it, eventually causing
the program and/or other concurrent processes to fail due to lack of memory.

A

memory leak

238
Q

A measurement scale and the method used for measurement.

A

metric

239
Q

A point in time in a project at which defined (intermediate) deliverables and results should be ready.

A

milestone

240
Q

Testing based on or involving models.

A

model-based testing (MBT)

241
Q

Operational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff focusing on
operational aspects, e.g., recoverability, resource-behavior, installability and technical compliance.

A

operational acceptance testing
See Also: operational testing
Synonyms: production acceptance testing

242
Q

Hardware and software products installed at users’ or customers’ sites where the component or system under test will be used. The software may include operating systems,
database management systems, and other applications.

A

operational environment

243
Q

A test is deemed to pass if its actual result matches its expected result.

A

pass

244
Q

A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.

A

path

Synonyms: control flow path

245
Q

A high-level metric of effectiveness and/or efficiency used to guide and control progressive development, e.g., lead-time slip for software development.

A

performance indicator

Synonyms: key performance indicator

246
Q

Testing to determine the performance of a software product.

A

performance testing

See Also: efficiency testing

247
Q

A consensus-based estimation technique, mostly used to estimate effort or relative size of user stories in Agile software development. It is a variation of the Wideband Delphi
method using a deck of cards with values representing the units in which the team estimates.

A

planning poker

248
Q

The ease with which the software product can be transferred from one hardware or software environment to another.

A

portability

249
Q

Testing to determine the portability of a software product.

A

portability testing

Synonyms: configuration testing

250
Q

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

A

priority

251
Q

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.

A

probe effect

252
Q

A set of interrelated activities, which transform inputs into outputs.

A

process

253
Q

A program of activities designed to improve the performance and maturity of the organization’s processes, and the result of such a program.

A

process improvement

254
Q

A risk impacting the quality of a product.

A

product risk

255
Q

A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements, including the
constraints of time, cost and resources.

A

project

256
Q

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

A

quality

257
Q

Part of quality management focused on providing confidence that quality requirements will be fulfilled.

A

quality assurance

258
Q

A category of product attributes that bears on quality.

A

quality characteristic

Synonyms: quality characteristic , software product characteristic , software quality characteristic , quality attribute

259
Q

The operational techniques and activities, part of quality management, that are focused on fulfilling quality requirements.

A

quality control

260
Q

Coordinated activities to direct and control an organization with regard to quality. Direction and control with regard to quality generally includes the establishment of the quality
policy and quality objectives, quality planning, quality control, quality assurance and quality improvement.

A

quality management

261
Q

A proprietary adaptable iterative software development process framework consisting of four project lifecycle phases: inception, elaboration, construction and transition.

A

Rational Unified Process (RUP)

262
Q

A model that shows the growth in reliability over time during continuous testing of a component or system as a result of the removal of defects that result in reliability failures.

A

reliability growth model

263
Q

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. Some requirements management tools also provide facilities for static analysis, such as consistency checking and
violations to pre-defined requirements rules.

A

requirements management tool

264
Q

A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project.

A

retrospective meeting

Synonyms: post-project meeting

265
Q

A type of static testing during which a work product or process is evaluated by one or more individuals to detect issues and to provide improvements.

A

review

266
Q

A document describing the approach, resources and schedule of intended review activities. It identifies, amongst others: documents and code to be reviewed, review types to
be used, participants, as well as entry and exit criteria to be applied in case of formal reviews, and the rationale for their choice. It is a record of the review planning process.

A

review plan

267
Q

A factor that could result in future negative consequences.

A

risk

268
Q

The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions.

A

robustness

269
Q

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

A

root cause

270
Q

An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is hoped that the likelihood of defect recurrence will be
minimized.

A

root cause analysis

Synonyms: causal analysis

271
Q

An iterative incremental framework for managing projects commonly used with Agile software development.

A

scrum

272
Q

The degree to which a component or system protects information and data so that persons or other components or systems have the degree of access appropriate to their
types and levels of authorization.

A

security

273
Q

Testing to determine the security of the software product.

A

security testing

See Also: functionality testing

274
Q

An approach to testing in which test activities are planned as uninterrupted sessions of test design and execution, often used in conjunction with exploratory testing.

A

session-based testing

275
Q

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

A

severity

276
Q

The representation of selected behavioral characteristics of one physical or abstract system by another system.

A

simulation

277
Q

A device, computer program or system used during testing, which behaves or operates like a given system when provided with a set of controlled inputs.

A

simulator

278
Q

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

A

software

279
Q

The period of time that begins when a software product is conceived and ends when the software is no longer available for use. The software lifecycle typically includes a
concept phase, requirements phase, design phase, implementation phase, test phase, installation and checkout phase, operation and maintenance phase, and sometimes,
retirement phase. Note these phases may overlap or be performed iteratively.

A

software lifecycle

280
Q

The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs.

A

software quality

281
Q

A document that specifies, ideally in a complete, precise and verifiable manner, the requirements, design, behavior, or other characteristics of a component or system, and,
often, the procedures for determining whether these provisions have been satisfied.

A

specification

282
Q

Formal, possibly mandatory, set of requirements developed and used to prescribe consistent approaches to the way of working or to provide guidelines (e.g., ISO/IEC
standards, IEEE standards, and organizational standards).

A

standard

283
Q

A diagram that depicts the states that a component or system can assume, and shows the events or circumstances that cause and/or result from a change from one state to
another.

A

state diagram

Synonyms: state transition diagram

284
Q

A transition between two states of a component or system.

A

state transition

285
Q

An entity in a programming language, which is typically the smallest indivisible unit of execution.

A

statement

Synonyms: source statement

286
Q

Coverage measures based on the internal structure of a component or system.

A

structural coverage

287
Q

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.

A

stub

288
Q

A collection of interacting elements organized to accomplish a specific function or set of functions.

A

system

289
Q

Testing the combination and interaction of systems.

A

System Integration Testing

290
Q

Testing an integrated system to verify that it meets specified requirements.

A

system testing

291
Q

A type of test object that is a system.

A

system under test (SUT)

292
Q

A set of one or more test cases.

A

test

293
Q

The use of software to perform or support test activities, e.g., test management, test design, test execution and results checking.

A

test automation

294
Q

The body of knowledge used as the basis for test analysis and design.

A

test basis

295
Q

A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.

A

test case

296
Q

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.

A

test control

297
Q

Execution of the test process against a single identifiable release of the test object.

A

test cycle

298
Q

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

A

test data preparation tool

299
Q

The activity of deriving and specifying test cases from test conditions.

A

test design

300
Q

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.

A

test design tool

301
Q

An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.

A

test environment

Synonyms: test bed , test rig

302
Q

The calculated approximation of a result related to various aspects of testing (e.g., effort spent, completion date, costs involved, number of test cases, etc.) which is usable
even if input data may be incomplete, uncertain, or noisy.

A

test estimation

303
Q

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

A

test execution

304
Q

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

A

test harness

305
Q

The activity that prepares the testware needed for test execution based on test analysis and design.

A

test implementation

306
Q

The organizational artifacts needed to perform testing, consisting of test environments, test tools, office environment and procedures.

A

test infrastructure

307
Q

The data received from an external source by the test object during test execution. The external source can be hardware, software or human.

A

test input

308
Q

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.

A

test management tool

309
Q

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.

A

test manager

310
Q

The component or system to be tested.

A

test object

311
Q

A reason or purpose for designing and executing a test.

A

test objective

312
Q

The activity of establishing or updating a test plan.

A

test planning

313
Q

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

A

test policy

Synonyms: organizational test policy

314
Q

A program of activities designed to improve the performance and maturity of the organization’s test processes and the results of such a program.

A

test process improvement

315
Q

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

A

test reporting

316
Q

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

A

test schedule

317
Q

A sequence of instructions for the execution of a test.

A

test script

318
Q

An uninterrupted period of time spent in executing tests. In exploratory testing, each test session 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.

A

test session

319
Q

A procedure used to derive and/or select test cases.

A

test technique

Synonyms: test case design technique , test specification technique , test technique , test design technique

320
Q

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.

A

test tool

321
Q

A requirements that is stated in terms that permit establishment of test designs (and subsequently test cases) and execution of tests to determine whether the requirement has
been met.

A

testable requirement

322
Q

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

A

tester

323
Q

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.

A

testing

324
Q

The capability of the software product to enable the user to understand whether the software is suitable, and how it can be used for particular tasks and conditions of use.

A

understandability

325
Q

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.

A

unit test framework

326
Q

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

A

unreachable code

Synonyms: dead code

327
Q

Testing to evaluate the degree to which the system can be used by specified users with effectiveness, efficiency and satisfaction in a specified context of use.

A

usability testing

328
Q

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.

A

use case

329
Q

All components of a system that provide information and controls for the user to accomplish specific tasks with the system.

A

user interface

330
Q

A high-level user or business requirement commonly used in Agile software development, typically consisting of one sentence in the everyday or business language capturing
what functionality a user needs and the reason behind this, any non-functional criteria, and also includes acceptance criteria.

A

user story

See Also: Agile software development, requirement

331
Q

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

A

validation

332
Q

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

A

variable

333
Q

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

A

verification

334
Q

A type of review in which an author leads members of the review through a work product and the members ask questions and make comments about possible issues.

A

walkthrough

Synonyms: structured walkthrough

335
Q

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

A

white-box testing
Synonyms: clear-box testing , code-based testing , glass-box testing , logic-coverage testing , logic-driven testing , structural testing , structure-based testing

336
Q

An expert-based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members.

A

Wideband Delphi

ISTQB Glossary (1 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions