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
2
Q
The degree to which a component or system uses
time, resources and capacity when accomplishing
its designated functions.
A
performance
efficiency
3
Q
A review technique carried out by independent reviewers informally,
without a structured process.
A
ad hoc reviewing
4
Q
A review technique guided by a list of questions or required attributes.
A
checklist-based
reviewing
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
6
Q
The degree to which a component or system can exchange information
with other components or systems.
A
compatibility
7
Q
Acceptance testing conducted to verify whether a system satisfies its
contractual requirements
A
contractual
acceptance testing
8
Q
The leader and main person responsible for an inspection or review
process.
A
facilitator
9
Q
An informal review performed by three or more persons.
A
informal group
review
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
11
Q
A review technique whereby reviewers evaluate the work product
from different viewpoints
A
perspective-based
reading
12
Q
An unknown underlying cause of one or more incidents.
A
problem
13
Q
A degradation in the quality of a component or system due to a
change
A
regression
14
Q
Acceptance testing conducted to verify whether a system conforms to
relevant laws, policies and regulations.
A
regulatory
acceptance testing
15
Q
A review technique where reviewers evaluate a work product from the
perspective of different stakeholder roles.
A
role-based
reviewing
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
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
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
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
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
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
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
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
24
Q
Documentation summarizing test activities and results
A
test report
25
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
black-box test
| technique
26
The number of defects found by a test level,
divided by the number found by that test level
and any other means afterwards
defect detection
| percentage
27
A procedure to derive and/or select test cases
based on the tester's experience, knowledge and
intuition.
experience-based
| test technique
28
A category of product attributes that bears on
| quality
quality characteristic
29
A procedure used to derive and/or select test
| cases
test technique
30
A procedure to derive and/or select test cases
based on an analysis of the internal structure of a
component or system.
white-box test
| technique
31
The criteria that a component or system must satisfy in order to be
accepted by a user, customer, or other authorized entity.
acceptance
| criteria
32
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.
accessibility
33
The degree to which a component or system can be adapted for
different or evolving hardware and software environments.
adaptability
34
Simulated or actual operational testing conducted in the
developer's test environment, by roles outside the development
organization
alpha testing
35
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.
analyzability
36
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.
audit
37
Simulated or actual operational testing conducted at an external
site, by roles outside the development organization.
beta testing
38
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.
big-bang testing
39
A minimum or maximum value of an ordered equivalence partition.
boundary value
40
A black-box test technique in which test cases are designed based
on boundary values.
boundary value
| analysis
41
The coverage of boundary values
boundary value
| coverage
42
A transfer of control from one location to a different location in the
code.
branch
43
The coverage of branches.
branch coverage
44
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.
checklist-based
| testing
45
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.
co-existence
46
A computer program that translates programs expressed in a high- order language into their machine language equivalents
compiler
47
A minimal part of a system that can be tested in isolation.
component
48
The testing of individual hardware or software components
component
| testing
49
An aggregation of work products that is designated for
configuration management and treated as a single entity in the
configuration management process.
configuration item
50
Dynamic testing conducted after fixing defects with the objective to
confirm that failures caused by those defects do not occur anymore.
confirmation
| testing
51
The sequence in which operations are performed during the
| execution of a test item.
control flow
52
A form of static analysis based on a control flow graph.
control flow
| analysis
53
An abstract representation of all possible control flows through a
component or system.
Control flow graph
54
A test technique in which test cases are designed on the basis of
control flows.
control flow
| testing
55
The degree to which specified coverage items have been
determined or have been exercised by a test suite expressed as a
percentage.
coverage
56
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.
coverage item
57
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).
cyclomatic
| complexity
58
A type of statement in which a choice between two or more
| possible outcomes controls which set of actions will result.
decision
59
The coverage of decision outcomes.
decision coverage
60
The result of a decision that determines the next statement to be
executed.
decision outcome
61
A table used to show sets of conditions and the actions resulting
from them.
decision table
62
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.
decision table
| testing
63
A white-box test technique in which test cases are designed to
execute decision outcomes.
decision testing
64
An imperfection or deficiency in a work product where it does not
meet its requirements or specifications.
defect
65
The number of defects per unit size of a work product.
defect density
66
The process of recognizing and recording defects, classifying them,
investigating them, taking action to resolve them, and disposing of
them when resolved.
defect
| management
67
A tool that facilitates the recording and status tracking of defects.
defect
| management tool
68
Documentation of the occurrence, nature, and status of a defect.
defect report
69
The set of conditions for officially starting a defined task.
entry criteria
70
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.
equivalence
| partition
71
A black-box test technique in which test cases are designed to
exercise equivalence partitions by using one representative
member of each partition.
equivalence
| partitioning
72
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.
error guessing
73
A defect that was not detected in a previous test level which is
supposed to find such type of defects.
escaped defect
74
The set of conditions for officially completing a defined task.
exit criteria
75
The predicted observable behavior of a component or system
executing under specified conditions, based on its specification or
another source.
expected result
76
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.
exploratory
| testing
77
An event in which a component or system does not perform a
| required function within specified limits.
failure
78
The ratio of the number of failures of a given category to a given
unit of measure.
failure rate
79
A form of review that follows a defined process with a formally
documented output.
formal review
80
A requirement that specifies a function that a component or system
must be able to perform.
functional
| requirement
81
Testing conducted to evaluate the compliance of a component or
system with functional requirements.
functional testing
82
A test case without concrete values for input data and expected
results.
high-level test
case
Synonyms: abstract test case , logical test case
83
The identification of all work products affected by a change,
including an estimate of the resources needed to accomplish the
change.
impact analysis
84
An event occurring that requires investigation.
incident
85
The process of recognizing and recording incidents, classifying
them, investigating them, taking action to resolve them, and
disposing of them when resolved.
incident
| management
86
A tool that facilitates the recording and status tracking of incidents.
incident
| management tool
87
Documentation of the occurrence, nature, and status of an incident.
incident report
88
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.
incremental
development
model
89
A measure that provides an estimate or evaluation of specified
attributes derived from a model with respect to defined information
needs.
indicator
90
A type of review without a formal (documented) procedure.
informal review
91
Data received by a component or system from an external source.
input
92
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.
inspection
93
The degree to which two or more components or systems can
exchange information and use the information that has been
exchanged.
interoperability
94
A description of the processes, workflows, and activities used in the
development, delivery, maintenance, and retirement of a system.
lifecycle model
95
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.
load testing
96
A test case with concrete values for input data and expected results.
low-level test case
97
The degree to which a component or system can be modified by the
intended maintainers.
maintainability
98
The process of modifying a component or system after delivery to
correct defects, improve quality attributes, or adapt to a changed
environment.
maintenance
99
A test plan that is used to coordinate multiple test levels or test
types.
master test plan
100
(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.
maturity
101
The coverage of model elements
model coverage
102
A neutral person who conducts a usability test session.
moderator
103
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.
monitoring tool
104
A requirement that describes how the component or system will do
what it is intended to do.
non-functional
| requirement
105
Testing conducted to evaluate the compliance of a component or
system with non-functional requirements.
non-functional
| testing
106
Model-based test approach whereby test cases are generated into a
repository for future execution.
offline MBT
107
Model-based test approach whereby test cases are generated and
executed simultaneously.
online MBT
108
An actual or predicted pattern of use of the component or system.
operational profile
109
Data transmitted by a component or system to an external
| destination.
output
110
An agile software development practice in which two programmers
work together on one workstation.
pair programming
111
The coverage of paths
path coverage
112
A form of review of work products performed by others qualified to
do the same work.
peer review
113
The expected state of a test item and its environment at the end of
test case execution.
postcondition
114
The required state of a test item and its environment prior to test
case execution.
precondition
115
A risk impacting the quality of a product.
product risk
116
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.
product-based
| quality
117
A risk that impacts project success.
project risk
118
A product risk related to a quality characteristic.
quality risk
119
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.
regression testing
120
The degree to which a component or system performs specified
functions under specified conditions for a specified period of time.
reliability
121
A provision that contains criteria to be fulfilled.
requirement
122
The period of time in the software lifecycle during which the
requirements for a software product are defined and documented.
requirements
| phase
123
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.
review
124
A participant in a review, who identifies issues in the work product.
reviewer
125
The overall process of risk identification and risk assessment.
risk analysis
126
The process to examine identified risks and determine the risk level.
risk assessment
127
The process of finding, recognizing and describing risks.
risk identification
128
The qualitative or quantitative measure of a risk defined by impact
and likelihood.
risk level
129
The coordinated activities to direct and control an organization with
regard to risk.
risk management
130
The process through which decisions are reached and protective
measures are implemented for reducing or maintaining risks to
specified levels.
risk mitigation
131
A set of risks grouped by one or more common factors.
risk type
132
Testing in which the management, selection, prioritization, and use
of testing activities and resources are based on corresponding risk
types and risk levels.
risk-based testing
133
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.
safety
134
A person who records information during the review meetings.
scribe
135
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.
security
136
The degree to which a component or system can be effectively and
efficiently modified without introducing defects or degrading
existing product quality.
stability
137
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.
state transition
| testing
138
A white-box test technique in which test cases are designed to
execute statements.
statement testing
139
The process of evaluating a component or system without executing
it, based on its form, structure, content, or documentation.
static analysis
140
Testing a work product without code being executed.
static testing
141
A collection of interacting elements organized to accomplish a
specific function or set of functions.
system
142
Testing the combination and interaction of systems.
System
Integration
Testing
143
A type of test object that is a system
system under test
144
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.
Systematic Test
and Evaluation
Process
145
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.
technical review
146
The activity that identifies test conditions by analyzing the test
basis.
test analysis
147
The implementation of the test strategy for a specific project.
test approach
148
The body of knowledge used as the basis for test analysis and
design.
test basis
149
A set of preconditions, inputs, actions (where applicable), expected
results and postconditions, developed based on test conditions.
test case
150
Documentation of a set of one or more test cases
test case
| specification
151
Documentation of test activities in session-based exploratory
testing.
test charter
152
An aspect of the test basis that is relevant in order to achieve
specific test objectives.
test condition
153
Data created or selected to satisfy the execution preconditions and
inputs to execute one or more test cases.
test data
154
The activity of deriving and specifying test cases from test
conditions.
test design
155
Documentation specifying the features to be tested and their
corresponding test conditions.
test design
| specification
156
A schedule for the execution of test suites within a test cycle.
test execution
| schedule
157
The activity that prepares the testware needed for test execution
based on test analysis and design.
test
| implementation
158
A part of a test object used in the test process.
test item
159
A specific instantiation of a test process.
test level
160
The activity of creating a test log.
test logging
161
The planning, scheduling, estimating, monitoring, reporting, control
and completion of test activities.
test management
162
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.
test monitoring
163
A source to determine expected results to compare with the actual
result of the system under test.
test oracle
164
Documentation describing the test objectives to be achieved and
the means and the schedule for achieving them, organized to
coordinate testing activities.
test plan
165
Documentation specifying one or more test procedures
test procedure
| specification
166
The set of interrelated activities comprising of test planning, test
monitoring and control, test analysis, test design, test
implementation, test execution, and test completion
test process
167
A test report produced at regular intervals about the progress of
test activities against a baseline, risks, and alternatives requiring a
decision.
test progress
| report
168
A sequence of instructions for the execution of a test.
test script
169
The complete documentation of the test design, test cases and test
procedures for a specific test item.
test specification
170
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.
test strategy
171
A set of test cases or test procedures to be executed in a specific
test cycle.
test suite
172
A test report that provides an evaluation of the corresponding test
items against exit criteria.
test summary
| report
173
A group of test activities based on specific test objectives aimed at
specific characteristics of a component or system.
test type
174
The degree of effectiveness and efficiency with which tests can be
designed and executed for a component or system.
testability
175
A review to evaluate the testability of the test basis.
testability review
176
Work products produced during the test process for use in planning,
designing, executing, evaluating and reporting on testing.
testware
177
The degree to which a relationship can be established between two
or more work products.
traceability
178
The degree to which a component or system can be used by
specified users to achieve specified goals in a specified context of
use.
usability
179
A black-box test technique in which test cases are designed to
execute scenarios of use cases.
use case testing
180
Acceptance testing conducted in a real or simulated operational
environment by intended users focusing their needs, requirements
and business processes.
user acceptance
| testing
181
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.
V-model
182
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.
walkthrough
183
Deliverable oriented hierarchical decomposition of the work to be
executed by the project team to accomplish the project objectives
(according to PMBOK).
work breakdown
| structure
184
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.
acceptance testing
185
Testing to determine the ease by which users with disabilities can use a component or system.
accessibility testing
186
The behavior produced/observed when a component or system is tested.
actual result
187
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.
anomaly
188
The degree to which a component or system is operational and accessible when required for use.
availability
189
The response of a component or system to a set of input values and preconditions.
behavior
190
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.
black-box test technique
191
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).
burndown chart
192
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
code coverage
193
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.
commercial off-the-shelf (COTS)
| Synonyms: off-the-shelf software
194
The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.
complexity
195
The capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions.
compliance
196
A minimal part of a system that can be tested in isolation.
Component
197
Testing performed to expose defects in the interfaces and interactions between integrated components.
component integration testing
| Synonyms: link testing
198
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).
component specification
199
A logical expression that can be evaluated as True or False, e.g., A>B.
condition
See Also: condition testing
Synonyms: branch condition
200
The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.
configuration
201
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.
configuration management
202
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.
configuration management tool
203
The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal failure costs and external failure costs.
cost of quality
204
A tool that provides objective measures of what structural elements, e.g., statements, branches have been exercised by a test suite.
coverage tool
205
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.
data flow
206
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.
data-driven testing
207
The process of finding, analyzing and removing the causes of failures in software.
debugging
208
A type of statement in which a choice between two or more possible outcomes controls which set of actions will result.
decision
209
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.
driver
| Synonyms: test driver
210
The process of evaluating behavior, e.g., memory performance, CPU usage, of a system or component during execution.
dynamic analysis
211
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.
dynamic analysis tool
212
Testing that involves the execution of the software of a component or system.
dynamic testing
213
Extent to which correct and complete goals are achieved.
effectiveness
214
Resources expended in relation to the extent with which users achieve specified goals.
efficiency
215
A human action that produces an incorrect result
error
216
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.
executable statement
217
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.
exercised
218
A test approach in which the test suite comprises all combinations of input values and preconditions.
exhaustive testing
| Synonyms: complete testing
219
Testing based on the tester's experience, knowledge and intuition.
experience-based testing
220
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.
Extreme Programming (XP)
221
A test is deemed to fail if its actual result does not match its expected result.
fail
222
An attribute of a component or system specified or implied by requirements documentation (for example reliability, usability or design constraints).
feature
| Synonyms: software feature
223
A result of an evaluation that identifies some important issue, problem, or opportunity.
finding
224
An integration approach that combines the components or systems for the purpose of getting a basic functionality working early.
functional integration
| See Also: integration testing
225
Acronym for Graphical User Interface.
GUI
226
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.
IDEAL
227
Separation of responsibilities, which encourages the accomplishment of objective testing.
independence of testing
228
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.
installation guide
229
The process of combining components or systems into larger assemblies.
integration
230
Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.
integration testing
231
Testing to determine the interoperability of a software product.
interoperability testing
See Also: functionality testing
Synonyms: compatibility testing
232
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.
iterative development model
233
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.
keyword-driven testing
See Also: data-driven testing
Synonyms: action word-driven testing
234
Testing the changes to an operational system or the impact of a changed environment to an operational system.
maintenance testing
235
The number or category assigned to an attribute of an entity by making a measurement.
measure
236
The process of assigning a number or category to an entity to describe an attribute of that entity.
measurement
237
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.
memory leak
238
A measurement scale and the method used for measurement.
metric
239
A point in time in a project at which defined (intermediate) deliverables and results should be ready.
milestone
240
Testing based on or involving models.
model-based testing (MBT)
241
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.
operational acceptance testing
See Also: operational testing
Synonyms: production acceptance testing
242
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.
operational environment
243
A test is deemed to pass if its actual result matches its expected result.
pass
244
A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
path
| Synonyms: control flow path
245
A high-level metric of effectiveness and/or efficiency used to guide and control progressive development, e.g., lead-time slip for software development.
performance indicator
| Synonyms: key performance indicator
246
Testing to determine the performance of a software product.
performance testing
| See Also: efficiency testing
247
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.
planning poker
248
The ease with which the software product can be transferred from one hardware or software environment to another.
portability
249
Testing to determine the portability of a software product.
portability testing
| Synonyms: configuration testing
250
The level of (business) importance assigned to an item, e.g., defect.
priority
251
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.
probe effect
252
A set of interrelated activities, which transform inputs into outputs.
process
253
A program of activities designed to improve the performance and maturity of the organization's processes, and the result of such a program.
process improvement
254
A risk impacting the quality of a product.
product risk
255
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.
project
256
The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.
quality
257
Part of quality management focused on providing confidence that quality requirements will be fulfilled.
quality assurance
258
A category of product attributes that bears on quality.
quality characteristic
| Synonyms: quality characteristic , software product characteristic , software quality characteristic , quality attribute
259
The operational techniques and activities, part of quality management, that are focused on fulfilling quality requirements.
quality control
260
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.
quality management
261
A proprietary adaptable iterative software development process framework consisting of four project lifecycle phases: inception, elaboration, construction and transition.
Rational Unified Process (RUP)
262
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.
reliability growth model
263
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.
requirements management tool
264
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.
retrospective meeting
| Synonyms: post-project meeting
265
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.
review
266
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.
review plan
267
A factor that could result in future negative consequences.
risk
268
The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions.
robustness
269
A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.
root cause
270
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.
root cause analysis
| Synonyms: causal analysis
271
An iterative incremental framework for managing projects commonly used with Agile software development.
scrum
272
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.
security
273
Testing to determine the security of the software product.
security testing
| See Also: functionality testing
274
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.
session-based testing
275
The degree of impact that a defect has on the development or operation of a component or system.
severity
276
The representation of selected behavioral characteristics of one physical or abstract system by another system.
simulation
277
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.
simulator
278
Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system.
software
279
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.
software lifecycle
280
The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs.
software quality
281
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.
specification
282
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).
standard
283
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.
state diagram
| Synonyms: state transition diagram
284
A transition between two states of a component or system.
state transition
285
An entity in a programming language, which is typically the smallest indivisible unit of execution.
statement
| Synonyms: source statement
286
Coverage measures based on the internal structure of a component or system.
structural coverage
287
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.
stub
288
A collection of interacting elements organized to accomplish a specific function or set of functions.
system
289
Testing the combination and interaction of systems.
System Integration Testing
290
Testing an integrated system to verify that it meets specified requirements.
system testing
291
A type of test object that is a system.
system under test (SUT)
292
A set of one or more test cases.
test
293
The use of software to perform or support test activities, e.g., test management, test design, test execution and results checking.
test automation
294
The body of knowledge used as the basis for test analysis and design.
test basis
295
A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.
test case
296
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.
test control
297
Execution of the test process against a single identifiable release of the test object.
test cycle
298
A type of test tool that enables data to be selected from existing databases or created, generated, manipulated and edited for use in testing.
test data preparation tool
299
The activity of deriving and specifying test cases from test conditions.
test design
300
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.
test design tool
301
An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
test environment
| Synonyms: test bed , test rig
302
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.
test estimation
303
The process of running a test on the component or system under test, producing actual result(s).
test execution
304
A test environment comprised of stubs and drivers needed to execute a test.
test harness
305
The activity that prepares the testware needed for test execution based on test analysis and design.
test implementation
306
The organizational artifacts needed to perform testing, consisting of test environments, test tools, office environment and procedures.
test infrastructure
307
The data received from an external source by the test object during test execution. The external source can be hardware, software or human.
test input
308
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.
test management tool
309
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.
test manager
310
The component or system to be tested.
test object
311
A reason or purpose for designing and executing a test.
test objective
312
The activity of establishing or updating a test plan.
test planning
313
A high-level document describing the principles, approach and major objectives of the organization regarding testing.
test policy
| Synonyms: organizational test policy
314
A program of activities designed to improve the performance and maturity of the organization's test processes and the results of such a program.
test process improvement
315
Collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform stakeholders.
test reporting
316
A list of activities, tasks or events of the test process, identifying their intended start and finish dates and/or times, and interdependencies.
test schedule
317
A sequence of instructions for the execution of a test.
test script
318
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.
test session
319
A procedure used to derive and/or select test cases.
test technique
| Synonyms: test case design technique , test specification technique , test technique , test design technique
320
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.
test tool
321
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.
testable requirement
322
A skilled professional who is involved in the testing of a component or system.
tester
323
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.
testing
324
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.
understandability
325
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.
unit test framework
326
Code that cannot be reached and therefore is impossible to execute.
unreachable code
| Synonyms: dead code
327
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.
usability testing
328
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.
use case
329
All components of a system that provide information and controls for the user to accomplish specific tasks with the system.
user interface
330
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.
user story
| See Also: Agile software development, requirement
331
Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.
validation
332
An element of storage in a computer that is accessible by a software program by referring to it by a name.
variable
333
Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.
verification
334
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.
walkthrough
| Synonyms: structured walkthrough
335
Testing based on an analysis of the internal structure of the component or system.
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
An expert-based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members.
Wideband Delphi
