ISTQB Foundation Level Exam Questions With
100% Correct Answers
.Acceptance testing (acceptance) - ANSWER-Formal testing with respect to user
needs, requirements, and business processes conducted to determine whether
or not a system satisfies the user's criteria.
.Accessibility - ANSWER-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 testing - ANSWER-Testing to determine the ease by which users
with disabilities can use a component or system.
.Actor - ANSWER-User or any other person or system that interacts with the test
object in a specific way.
.Actual result (Actual outcome) - ANSWER-The behavior produced/observed
when a component or system is tested.
.Ad hoc reviewing - ANSWER-A review technique carried out by independent
reviewers informally, without a structured process.
.Alpha testing - ANSWER-Simulated or actual operational testing by potential
users/customers or an independent test team at the developers' site, but
outside the development organization.
,.Anomaly - ANSWER-Any condition that deviates from expectation based on
requirement specifications, design documents, user documents, standards, etc.
or from someone's perception or experience. They may be found, but not
limited to, in reviewing, testing, analysis, compilation, or use of software
products or applicable documentation.
.Attack (fault attack)* - ANSWER-Directed and focused attempt to evaluate the
quality, especially reliability, of a test object by attempting to force specific
failures to occur.
.Audit - ANSWER-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.
.Availability - ANSWER-The degree to which a component or system is
operational and accessible when required for use.
.Basis test set - ANSWER-Test cases derived from the internal structure of a
component or specification to ensure that 100% of a specified coverage
criterion will be achieved.
.Behavior - ANSWER-The response of a component or system to a set of input
values and preconditions.
.Beta testing (field testing) - ANSWER-Simulated or actual operational testing
conducted at an external site, by roles outside the development organization.
,.Big-bang testing* - ANSWER-A type of integration testing in which software
elements, hardware elements, or both are combined all at once into a
component or an overall system, rather than in stages.
.Black box test technique (non-functional test design technique, specification-
based test design technique) - ANSWER-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.
.Boundary value - ANSWER-A minimum or maximum value of an ordered
equivalence partition..
.Boundary value analysis - ANSWER-A black box test design technique in which
test cases are designed based on values at the edge of an equivalence partition.
.Boundary value coverage* - ANSWER-The percentage of boundary values that
have been exercised by a test suite.
.Burndown chart - ANSWER-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).
.Call graph* - ANSWER-An abstract representation of calling relationships
between subroutines in a program.
.Certification* - ANSWER-The process of confirming that a component, system
or person complies with its specified requirements, e.g. by passing an exam.
, .Checklist-based reviewing - ANSWER-A review technique guided by a list of
questions or required attributes.
.Checklist-based testing - ANSWER-An experience-based test design technique
in which the experienced tester uses a high-level list of items or a set of rules or
criteria against which a product has to be verified.
.Code coverage - ANSWER-An analysis method that determines which parts of
the software have been executed by the test suite and which parts have not
been executed.
.Code* - ANSWER-Computer instruction and data definitions expressed in a
programming language or in a form of output by an assembler, compiler, or
other translator.
.Coding standard - ANSWER-A description of the characteristics of a design or a
design description of data or program components.
.Commercial off-the-shelf software/COTS (off-the-shelf software) - ANSWER-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.
.Compatibility - ANSWER-The degree to which a component or system can
exchange information with other components or systems, and/or perform its
required functions while sharing the same hardware or software environment.
100% Correct Answers
.Acceptance testing (acceptance) - ANSWER-Formal testing with respect to user
needs, requirements, and business processes conducted to determine whether
or not a system satisfies the user's criteria.
.Accessibility - ANSWER-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 testing - ANSWER-Testing to determine the ease by which users
with disabilities can use a component or system.
.Actor - ANSWER-User or any other person or system that interacts with the test
object in a specific way.
.Actual result (Actual outcome) - ANSWER-The behavior produced/observed
when a component or system is tested.
.Ad hoc reviewing - ANSWER-A review technique carried out by independent
reviewers informally, without a structured process.
.Alpha testing - ANSWER-Simulated or actual operational testing by potential
users/customers or an independent test team at the developers' site, but
outside the development organization.
,.Anomaly - ANSWER-Any condition that deviates from expectation based on
requirement specifications, design documents, user documents, standards, etc.
or from someone's perception or experience. They may be found, but not
limited to, in reviewing, testing, analysis, compilation, or use of software
products or applicable documentation.
.Attack (fault attack)* - ANSWER-Directed and focused attempt to evaluate the
quality, especially reliability, of a test object by attempting to force specific
failures to occur.
.Audit - ANSWER-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.
.Availability - ANSWER-The degree to which a component or system is
operational and accessible when required for use.
.Basis test set - ANSWER-Test cases derived from the internal structure of a
component or specification to ensure that 100% of a specified coverage
criterion will be achieved.
.Behavior - ANSWER-The response of a component or system to a set of input
values and preconditions.
.Beta testing (field testing) - ANSWER-Simulated or actual operational testing
conducted at an external site, by roles outside the development organization.
,.Big-bang testing* - ANSWER-A type of integration testing in which software
elements, hardware elements, or both are combined all at once into a
component or an overall system, rather than in stages.
.Black box test technique (non-functional test design technique, specification-
based test design technique) - ANSWER-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.
.Boundary value - ANSWER-A minimum or maximum value of an ordered
equivalence partition..
.Boundary value analysis - ANSWER-A black box test design technique in which
test cases are designed based on values at the edge of an equivalence partition.
.Boundary value coverage* - ANSWER-The percentage of boundary values that
have been exercised by a test suite.
.Burndown chart - ANSWER-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).
.Call graph* - ANSWER-An abstract representation of calling relationships
between subroutines in a program.
.Certification* - ANSWER-The process of confirming that a component, system
or person complies with its specified requirements, e.g. by passing an exam.
, .Checklist-based reviewing - ANSWER-A review technique guided by a list of
questions or required attributes.
.Checklist-based testing - ANSWER-An experience-based test design technique
in which the experienced tester uses a high-level list of items or a set of rules or
criteria against which a product has to be verified.
.Code coverage - ANSWER-An analysis method that determines which parts of
the software have been executed by the test suite and which parts have not
been executed.
.Code* - ANSWER-Computer instruction and data definitions expressed in a
programming language or in a form of output by an assembler, compiler, or
other translator.
.Coding standard - ANSWER-A description of the characteristics of a design or a
design description of data or program components.
.Commercial off-the-shelf software/COTS (off-the-shelf software) - ANSWER-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.
.Compatibility - ANSWER-The degree to which a component or system can
exchange information with other components or systems, and/or perform its
required functions while sharing the same hardware or software environment.
