ISTQB Foundation level exam question
with answers
Error - User made mistake in using the software, this may lead directly to a problem
-defect - flaws in the software itself
-acceptance criteria - The exit criteria that a component or system must satisfy in
order to be accepted
by a user, customer, or other authorized entity.
-acceptance testing - 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.
-accessibility testing - Testing to determine the ease by which users with
disabilities can use a component or system.
-accuracy - The capability of the software product to provide the right or agreed
results or effects with the needed degree of precision.
-accuracy testing - The process of testing to determine the accuracy of a software
product. See also accuracy.
-acting (IDEAL) - The phase within the IDEAL model where the improvements are
developed, put into practice, and deployed across the organization. The acting
phase consists of the activities: create solution, pilot/test solution, refine solution
and implement solution.
-actor - User or any other person or system that interacts with the system under
test in a specific way
-actual result - The behavior produced/observed when a component or system is
tested.
-ad hoc testing - Testing carried out informally; no formal test preparation takes
place, no recognized test design technique is used, there are no expectations for
results and arbitrariness guides the test execution activity.
-adaptability - The capability of the software product to be adapted for different
specified environments without applying actions or means other than those
provided for this purpose for the software considered.
-agile manifesto - F-AT agile manifesto: A statement on the values that underpin
agile software development. The values are:
- individuals and interactions over processes and tools - working software over
comprehensive documentation - customer collaboration over contract negotiation
, - responding to change over following a plan.
-agile software development: - A group of software development methodologies
based on
EITP iterative incremental development, where requirements and solutions evolve
through collaboration
between self-organizing cross-functional teams.
-agile testing - Testing practice for a project using agile software development
methodologies, incorporating techniques and methods, such as extreme
programming (XP), treating development as the customer of testing and
emphasizing the test-first design paradigm. See also test-driven development.
-alpha testing - simulated or actual operational testing by potential
users/customers or an independent test team at the developers' site, but outside
the development organization. Alpha testing is often employed for off-the-shelf
software as a form of internal acceptance testing.
-analytical testing - Testing based on a systematic analysis of e.g., product risks or
requirements.
-analyzability - The capability of the software product to be diagnosed for
deficiencies or causes of failures in the software, or for the parts to be modified to
be identified.
-anomaly - 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.
-anti-pattern - Repeated action, process, structure or reusable solution that initially
appears to be beneficial and is commonly used but is ineffective and/or
counterproductive in practice.
-API - Acronym for Application Programming Interface.
-API testing - Testing performed by submitting commands to the software under
test using
programming interfaces of the application directly.
-assessment report - A document summarizing the assessment results, e.g.
conclusions, recommendations and findings. See also process assessment.
-assessor - A person who conducts an assessment; any member of an assessment
team.
-atomic condition - A condition that cannot be decomposed, i.e., a condition that
does not contain two
or more single conditions joined by a logical operator (AND, OR, XOR
with answers
Error - User made mistake in using the software, this may lead directly to a problem
-defect - flaws in the software itself
-acceptance criteria - The exit criteria that a component or system must satisfy in
order to be accepted
by a user, customer, or other authorized entity.
-acceptance testing - 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.
-accessibility testing - Testing to determine the ease by which users with
disabilities can use a component or system.
-accuracy - The capability of the software product to provide the right or agreed
results or effects with the needed degree of precision.
-accuracy testing - The process of testing to determine the accuracy of a software
product. See also accuracy.
-acting (IDEAL) - The phase within the IDEAL model where the improvements are
developed, put into practice, and deployed across the organization. The acting
phase consists of the activities: create solution, pilot/test solution, refine solution
and implement solution.
-actor - User or any other person or system that interacts with the system under
test in a specific way
-actual result - The behavior produced/observed when a component or system is
tested.
-ad hoc testing - Testing carried out informally; no formal test preparation takes
place, no recognized test design technique is used, there are no expectations for
results and arbitrariness guides the test execution activity.
-adaptability - The capability of the software product to be adapted for different
specified environments without applying actions or means other than those
provided for this purpose for the software considered.
-agile manifesto - F-AT agile manifesto: A statement on the values that underpin
agile software development. The values are:
- individuals and interactions over processes and tools - working software over
comprehensive documentation - customer collaboration over contract negotiation
, - responding to change over following a plan.
-agile software development: - A group of software development methodologies
based on
EITP iterative incremental development, where requirements and solutions evolve
through collaboration
between self-organizing cross-functional teams.
-agile testing - Testing practice for a project using agile software development
methodologies, incorporating techniques and methods, such as extreme
programming (XP), treating development as the customer of testing and
emphasizing the test-first design paradigm. See also test-driven development.
-alpha testing - simulated or actual operational testing by potential
users/customers or an independent test team at the developers' site, but outside
the development organization. Alpha testing is often employed for off-the-shelf
software as a form of internal acceptance testing.
-analytical testing - Testing based on a systematic analysis of e.g., product risks or
requirements.
-analyzability - The capability of the software product to be diagnosed for
deficiencies or causes of failures in the software, or for the parts to be modified to
be identified.
-anomaly - 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.
-anti-pattern - Repeated action, process, structure or reusable solution that initially
appears to be beneficial and is commonly used but is ineffective and/or
counterproductive in practice.
-API - Acronym for Application Programming Interface.
-API testing - Testing performed by submitting commands to the software under
test using
programming interfaces of the application directly.
-assessment report - A document summarizing the assessment results, e.g.
conclusions, recommendations and findings. See also process assessment.
-assessor - A person who conducts an assessment; any member of an assessment
team.
-atomic condition - A condition that cannot be decomposed, i.e., a condition that
does not contain two
or more single conditions joined by a logical operator (AND, OR, XOR
