ISTQB Foundation Level
Acceptance testing - ------------ANS: Also known as Acceptance. Formal testing with
respect to user needs, requirements and business processes conducted to
determine whether or not a system satisfied the acceptance criteria and to enable
the users. customers, or other authorized entities to determine whether or not to
accept the system.
Acceptance testing (acceptance, user acceptance testing) - ------------ANS: 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 - ------------ANS: Testing to determine the ease by which user
with disabilities can use a component or system.
Accuracy - ------------ANS: The capability of the software product to provide the right
or agreed results or effects with the needed degree of precision.
Accuracy testing - ------------ANS: The process of testing to determine the accuracy
of a software product.
Acting (IDEAL) - ------------ANS: 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.
Actual result - ------------ANS: Also known as Actual outcome. The behavior
produced/observed when a component or system is tested.
,Adaptability - ------------ANS: 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.
Adhoc testing - ------------ANS: 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.
Agile manifesto - ------------ANS: 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 - ------------ANS: A group of software development
methodologies based on iterative incremental development., where requirements
and solutions evolve through collaboration between self-organizing cross-functional
teams.
Agile testing - ------------ANS: Testing practice for a project using agile methodologies
such as extreme programming (XP), treating development a the customer of testing
and emphasizing the test-first design paradigm.
Alpha testing - ------------ANS: 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.
Analyzability - ------------ANS: 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 - ------------ANS: Any condition that deviates from expectation based on
requirement specifications, design documents, user documents, standards, etc. or
,from someone's perception or experience. Anomalies may be found but not limited
to, reviewing testing, analysis, compilation, or use of software products or applicable
documentation.
Assessment report - ------------ANS: A document summarizing the assessment
results, e.g. conclusions, recommendations and findings.
Assessor - ------------ANS: A person who conducts an assessment; any member of
an assessment team.
Attack - ------------ANS: Directed and focused attempt to evaluate the quality,
especially reliability of a test object by attempting to force specific failures to occur.
Attractiveness - ------------ANS: The capability of he software product to be attractive
to the user.
Audit - ------------ANS: An independent evaluation of software products or processes
to ascertain compliance to standards, guidelines, specifications, and/or procedures
based on objective criteria, including documents that specify: 1. Form or content of
products to be produced; 2. The process by which the products shall be produced; 3.
How compliance to standards or guidelines shall be measured.
Audit trail - ------------ANS: A path by which the original input to a process (e.g. data)
can be traced back through the process, taking the process output as a starting
point. This facilitates defect analysis and allows a process audit to be carried out.
Automated testware - ------------ANS: Testware used in automation testing, such as
tool scripts.
Availability - ------------ANS: The degree to which a component or system is
operational and accessible when required for use. Often expressed as a percentage.
, Back-to-back testing - ------------ANS: Testing in which two or more variants of a
component or system are executed with the same inputs, the outputs compared, and
analyzed in cases or discrepancies.
Balanced scorecard - ------------ANS: A strategic performance management tool for
measuring whether the operational activities of a company are aligned with its
objectives in terms of business vision and strategy.
Baseline - ------------ANS: A specification or software product that has been formally
reviewed or agreed upon that thereafter serves as the basis for further development,
and that can be changed only through a formal change control process.
Basic block - ------------ANS: A sequence of one or more consecutive executable
statements containing no branches.
Basic block set - ------------ANS: A set of test cases derived from the internal
structure of a component or specification to ensure that 100% of a specified
coverage criteria will be achieved.
Behavior - ------------ANS: The response of a component or system to a set of input
values and preconditions.
Benchmark test - ------------ANS: 1. A standard against which measurements or
comparisons can be made. 2. A test that is used to compare component or systems
to each other or to a standard as in 1.
Bespoke software - ------------ANS: Also known as customer software. Software
developed specifically for a set of users or customers. The opposite is off-the-shelf
software.
Acceptance testing - ------------ANS: Also known as Acceptance. Formal testing with
respect to user needs, requirements and business processes conducted to
determine whether or not a system satisfied the acceptance criteria and to enable
the users. customers, or other authorized entities to determine whether or not to
accept the system.
Acceptance testing (acceptance, user acceptance testing) - ------------ANS: 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 - ------------ANS: Testing to determine the ease by which user
with disabilities can use a component or system.
Accuracy - ------------ANS: The capability of the software product to provide the right
or agreed results or effects with the needed degree of precision.
Accuracy testing - ------------ANS: The process of testing to determine the accuracy
of a software product.
Acting (IDEAL) - ------------ANS: 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.
Actual result - ------------ANS: Also known as Actual outcome. The behavior
produced/observed when a component or system is tested.
,Adaptability - ------------ANS: 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.
Adhoc testing - ------------ANS: 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.
Agile manifesto - ------------ANS: 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 - ------------ANS: A group of software development
methodologies based on iterative incremental development., where requirements
and solutions evolve through collaboration between self-organizing cross-functional
teams.
Agile testing - ------------ANS: Testing practice for a project using agile methodologies
such as extreme programming (XP), treating development a the customer of testing
and emphasizing the test-first design paradigm.
Alpha testing - ------------ANS: 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.
Analyzability - ------------ANS: 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 - ------------ANS: Any condition that deviates from expectation based on
requirement specifications, design documents, user documents, standards, etc. or
,from someone's perception or experience. Anomalies may be found but not limited
to, reviewing testing, analysis, compilation, or use of software products or applicable
documentation.
Assessment report - ------------ANS: A document summarizing the assessment
results, e.g. conclusions, recommendations and findings.
Assessor - ------------ANS: A person who conducts an assessment; any member of
an assessment team.
Attack - ------------ANS: Directed and focused attempt to evaluate the quality,
especially reliability of a test object by attempting to force specific failures to occur.
Attractiveness - ------------ANS: The capability of he software product to be attractive
to the user.
Audit - ------------ANS: An independent evaluation of software products or processes
to ascertain compliance to standards, guidelines, specifications, and/or procedures
based on objective criteria, including documents that specify: 1. Form or content of
products to be produced; 2. The process by which the products shall be produced; 3.
How compliance to standards or guidelines shall be measured.
Audit trail - ------------ANS: A path by which the original input to a process (e.g. data)
can be traced back through the process, taking the process output as a starting
point. This facilitates defect analysis and allows a process audit to be carried out.
Automated testware - ------------ANS: Testware used in automation testing, such as
tool scripts.
Availability - ------------ANS: The degree to which a component or system is
operational and accessible when required for use. Often expressed as a percentage.
, Back-to-back testing - ------------ANS: Testing in which two or more variants of a
component or system are executed with the same inputs, the outputs compared, and
analyzed in cases or discrepancies.
Balanced scorecard - ------------ANS: A strategic performance management tool for
measuring whether the operational activities of a company are aligned with its
objectives in terms of business vision and strategy.
Baseline - ------------ANS: A specification or software product that has been formally
reviewed or agreed upon that thereafter serves as the basis for further development,
and that can be changed only through a formal change control process.
Basic block - ------------ANS: A sequence of one or more consecutive executable
statements containing no branches.
Basic block set - ------------ANS: A set of test cases derived from the internal
structure of a component or specification to ensure that 100% of a specified
coverage criteria will be achieved.
Behavior - ------------ANS: The response of a component or system to a set of input
values and preconditions.
Benchmark test - ------------ANS: 1. A standard against which measurements or
comparisons can be made. 2. A test that is used to compare component or systems
to each other or to a standard as in 1.
Bespoke software - ------------ANS: Also known as customer software. Software
developed specifically for a set of users or customers. The opposite is off-the-shelf
software.
