ISTQB Foundation Level Exam Questions and Answers Latest Update 2025 Already Passed
Error (Mistake) - Answers A human action that produces an incorrect result
Failure - Answers An event in which a component or system does not perform a required function within
specified limits.
Quality - Answers The degree to which a component, system or process meets specified requirements
and/or user/customer needs and expectations.
Risk - Answers A factor that could result in future negative consequences; usually expressed as impact
and likelihood.
Testing (evaluation) - Answers The process consisting of all life-cycle activities both static and dynamic,
concerned with planning, preparation, and evaluation of software products and related work products
to determine that they are fit for purpose, and to detect defects.
Requirement - Answers A provision that contains criteria to be fulfilled.
Review - Answers 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.
Debugging - Answers The process of finding, analyzing, and removing the causes of failures in software.
Confirmation testing (re-testing) - Answers Dynamic testing conducted after fixing defects with the
objective to confirm that failures caused by those defects do not occur anymore.
Test Strategy (Organizational test strategy) - Answers High-level documentation that expresses the
generic requirements for assessing 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 Execution - Answers The process of executing code in the component or system under test,
producing actual results
Test approach - Answers The implementation of the test strategy for a specific project.
Test Plan - Answers Documentation organized to coordinate testing activities by describing the
objectives and means of achieving them, as well as the schedule within which such achievements are to
be completed.
Test monitoring - Answers A 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 condition (test requirement, test situation) - Answers An aspect of the test basis that is relevant in
order to achieve specific test objectives.
Test basis - Answers The body of knowledge on which assessment analysis and design are based.
,Test Data - Answers Inputs created or selected to satisfy the execution preconditions and to execute one
or more test cases.
Coverage (test coverage) - Answers The degree, expressed as a percentage, to which specified items
have been exercised by a test suite.
Test procedure - Answers 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.
Test Suite (Test case suite, test set) - Answers A set of test cases or test procedures to be executed in a
specific test cycle.
Incident* (deviation) - Answers Any event occurring that requires investigation.
Testware - Answers Work products produced during the test process for use in planning, designing,
executing, evaluating and reporting on testing.
Regression testing - Answers Assessment of a previously tested program following modification to
ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a
result of the changes made.
Test log* - Answers A chronological record of relevant details about the execution of assessments.
Independence of testing - Answers Separation of responsibilities, which encourages the accomplishment
of objective testing
Test policy (Organizational test policy) - Answers A high-level document describing an organization's
principles, approach, and major objectives regarding assessment.
Verification - Answers Confirmation by examination of software specifications and through the provision
of objective evidence that specified requirements have been fulfilled.
Validation - Answers Confirmation by examination and through the provision of objective evidence that
the requirements for a specific intended use or application have been fulfilled.
V-model - Answers 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.
Test level - Answers Groups of test activities that are organized and managed together, performed in
relation to software at a given stage of development. Each one is an instance of the test process.
Integration - Answers The process of combining components or systems into larger assemblies.
Commercial off-the-shelf software/COTS (off-the-shelf software) - Answers 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.
, Performance* - Answers The degree to which a system or component accomplishes its designated
functions within given constraints regarding processing time and throughput rate.
Incremental development model - Answers A code design model in which the component or system is
delivered in a series of steps.
Iterative development model - Answers A design and coding lifecycle in which the component or system
is developed through a series of repeated cycles.
Component testing (unit testing, module testing) - Answers The testing of individual hardware or
software units or modules.
Stub - Answers 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.
Robustness testing* - Answers Testing to determine how well a product can function under stressful
conditions.
Integration testing - Answers Testing performed to expose defects in the interfaces and in the
interactions between combined components or systems.
System testing - Answers The process of assessing a collection of interacting elements to verify that it
meets specified requirements.
Functional requirement - Answers A specification that determines behavior that a component or system
must perform.
Non-functional requirement - Answers A requirement that describes how [or how well] the component
or system will do what it is intended to do.
Test environment (test bed, test rig) - Answers A setting containing hardware, instrumentations,
simulators, software tools, and other support elements needed to conduct a test.
Acceptance testing (acceptance) - Answers Formal testing with respect to user needs, requirements, and
business processes conducted to determine whether or not a system satisfies the user's criteria.
Maintenance - Answers Modification of a software product after delivery to correct defects, to improve
performance or other attributes or to adapt the product to a changed environment.
Alpha testing - Answers Simulated or actual operational testing by potential users/customers or an
independent test team at the developers' site, but outside the development organization.
Beta testing (field testing) - Answers Simulated or actual operational testing conducted at an external
site, by roles outside the development organization.
Test Type - Answers A group of test activities based on specific test objectives aimed at specific
characteristics of a component or system.
Error (Mistake) - Answers A human action that produces an incorrect result
Failure - Answers An event in which a component or system does not perform a required function within
specified limits.
Quality - Answers The degree to which a component, system or process meets specified requirements
and/or user/customer needs and expectations.
Risk - Answers A factor that could result in future negative consequences; usually expressed as impact
and likelihood.
Testing (evaluation) - Answers The process consisting of all life-cycle activities both static and dynamic,
concerned with planning, preparation, and evaluation of software products and related work products
to determine that they are fit for purpose, and to detect defects.
Requirement - Answers A provision that contains criteria to be fulfilled.
Review - Answers 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.
Debugging - Answers The process of finding, analyzing, and removing the causes of failures in software.
Confirmation testing (re-testing) - Answers Dynamic testing conducted after fixing defects with the
objective to confirm that failures caused by those defects do not occur anymore.
Test Strategy (Organizational test strategy) - Answers High-level documentation that expresses the
generic requirements for assessing 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 Execution - Answers The process of executing code in the component or system under test,
producing actual results
Test approach - Answers The implementation of the test strategy for a specific project.
Test Plan - Answers Documentation organized to coordinate testing activities by describing the
objectives and means of achieving them, as well as the schedule within which such achievements are to
be completed.
Test monitoring - Answers A 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 condition (test requirement, test situation) - Answers An aspect of the test basis that is relevant in
order to achieve specific test objectives.
Test basis - Answers The body of knowledge on which assessment analysis and design are based.
,Test Data - Answers Inputs created or selected to satisfy the execution preconditions and to execute one
or more test cases.
Coverage (test coverage) - Answers The degree, expressed as a percentage, to which specified items
have been exercised by a test suite.
Test procedure - Answers 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.
Test Suite (Test case suite, test set) - Answers A set of test cases or test procedures to be executed in a
specific test cycle.
Incident* (deviation) - Answers Any event occurring that requires investigation.
Testware - Answers Work products produced during the test process for use in planning, designing,
executing, evaluating and reporting on testing.
Regression testing - Answers Assessment of a previously tested program following modification to
ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a
result of the changes made.
Test log* - Answers A chronological record of relevant details about the execution of assessments.
Independence of testing - Answers Separation of responsibilities, which encourages the accomplishment
of objective testing
Test policy (Organizational test policy) - Answers A high-level document describing an organization's
principles, approach, and major objectives regarding assessment.
Verification - Answers Confirmation by examination of software specifications and through the provision
of objective evidence that specified requirements have been fulfilled.
Validation - Answers Confirmation by examination and through the provision of objective evidence that
the requirements for a specific intended use or application have been fulfilled.
V-model - Answers 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.
Test level - Answers Groups of test activities that are organized and managed together, performed in
relation to software at a given stage of development. Each one is an instance of the test process.
Integration - Answers The process of combining components or systems into larger assemblies.
Commercial off-the-shelf software/COTS (off-the-shelf software) - Answers 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.
, Performance* - Answers The degree to which a system or component accomplishes its designated
functions within given constraints regarding processing time and throughput rate.
Incremental development model - Answers A code design model in which the component or system is
delivered in a series of steps.
Iterative development model - Answers A design and coding lifecycle in which the component or system
is developed through a series of repeated cycles.
Component testing (unit testing, module testing) - Answers The testing of individual hardware or
software units or modules.
Stub - Answers 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.
Robustness testing* - Answers Testing to determine how well a product can function under stressful
conditions.
Integration testing - Answers Testing performed to expose defects in the interfaces and in the
interactions between combined components or systems.
System testing - Answers The process of assessing a collection of interacting elements to verify that it
meets specified requirements.
Functional requirement - Answers A specification that determines behavior that a component or system
must perform.
Non-functional requirement - Answers A requirement that describes how [or how well] the component
or system will do what it is intended to do.
Test environment (test bed, test rig) - Answers A setting containing hardware, instrumentations,
simulators, software tools, and other support elements needed to conduct a test.
Acceptance testing (acceptance) - Answers Formal testing with respect to user needs, requirements, and
business processes conducted to determine whether or not a system satisfies the user's criteria.
Maintenance - Answers Modification of a software product after delivery to correct defects, to improve
performance or other attributes or to adapt the product to a changed environment.
Alpha testing - Answers Simulated or actual operational testing by potential users/customers or an
independent test team at the developers' site, but outside the development organization.
Beta testing (field testing) - Answers Simulated or actual operational testing conducted at an external
site, by roles outside the development organization.
Test Type - Answers A group of test activities based on specific test objectives aimed at specific
characteristics of a component or system.
