ISTQB CTFL - Chapters 1-6

CTFL 4.0 (2022)

acceptance testing

A test level that focuses on determining whether to accept the system.

black-box testing

Testing based on an analysis of the specification of the component or system.

component integration testing

The integration testing of components.

component testing

A test level that focuses on individual hardware or software components.

confirmation testing

A type of change-related testing performed after fixing a defect to confirm that a failure caused by that defect does not reoccur.

functional testing

Testing performed to evaluate if a component or system satisfies functional requirements.

integration testing

A test level that focuses on interactions between components or systems.

maintenance testing

Testing the changes to an operational system or the impact of a changed environment to an operational system.

non-functional testing

Testing performed to evaluate that a component or system complies with non-functional requirements.

regression testing

A type of change-related testing to detect whether defects have been introduced or uncovered in unchanged areas of the software.

shift-left

An approach to performing testing and quality assurance activities as early as possible in the software development lifecycle.

system integration testing

The integration testing of systems.

system testing

A test level that focuses on verifying that a system as a whole meets specified requirements.

test level

A specific instantiation of a test process.

test object

The work product to be tested.

test type

A group of test activities based on specific test objectives aimed at specific characteristics of a component or system.

white-box testing

Testing based on an analysis of the internal structure of the component or system.

acceptance criteria

The criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.

acceptance test-driven development

A collaboration-based test-first approach that defines acceptance tests in the stakeholders' domain language.

black-box test technique

A test technique based on an analysis of the specification of a component or system.

boundary value analysis

A black-box test technique in which test cases are designed based on boundary values.

branch coverage

The coverage of branches in a control flow graph.

checklist-based testing

An experience-based test technique in which test cases are designed to exercise the items of a checklist.

collaboration-based test approach

An approach to testing that focuses on defect avoidance by collaborating among stakeholders.

coverage

The degree to which specified coverage items are exercised by a test suite, expressed as a percentage.

coverage item

An attribute or combination of attributes derived from one or more test conditions by using a test technique.

decision table testing

A black-box test technique in which test cases are designed to exercise the combinations of conditions and the resulting actions shown in a decision table.

equivalence partitioning

A black-box test technique in which test conditions are equivalence partitions exercised by one representative member of each partition.

error guessing

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.

experience-based test technique

A test technique based on the tester's experience, knowledge and intuition.

exploratory testing

An approach to testing in which the testers dynamically design and execute tests based on their knowledge, exploration of the test item and the results of previous tests.

state transition testing

A black-box test technique in which test cases are designed to exercise elements of a state transition model.

statement coverage

The coverage of executable statements.

test technique

A procedure used to define test conditions, design test cases, and specify test data.

white-box test technique

A test technique only based on the internal structure of a component or system.

anomaly

A condition that deviates from expectation.

dynamic testing

Testing that involves the execution of the test item.

formal review

A type of review that follows a defined process with a formally documented output.

informal review

A type of review that does not follow a defined process and has no formally documented output.

inspection

A type of formal review that uses defined team roles and measurement to identify defects in a work product, and improve the review process and the software development process.

review

A type of static testing in which a work product or process is evaluated by one or more individuals to detect defects or to provide improvements.

static analysis

The process of evaluating a component or system without executing it, based on its form, structure, content, or documentation.

static testing

Testing that does not involve the execution of a test item.

technical review

A formal review by technical experts that examine the quality of a work product and identify discrepancies from specifications and standards.

walkthrough

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.

coverage

The degree to which specified coverage items are exercised by a test suite, expressed as a percentage.

debugging

The process of finding, analyzing and removing the causes of failures in a component or system.

defect

An imperfection or deficiency in a work product where it does not meet its requirements or specifications.

error

A human action that produces an incorrect result.

failure

An event in which a component or system does not perform a required function within specified limits.

quality

The degree to which a work product satisfies stated and implied needs of its stakeholders.

quality assurance

Activities focused on providing confidence that quality requirements will be fulfilled.

root cause

A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.

test analysis

The activity that identifies test conditions by analyzing the test basis.

test basis

The body of knowledge used as the basis for test analysis and design.

test case

A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.

test completion

The activity that makes testware available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to relevant stakeholders.

test condition

A testable aspect of a component or system identified as a basis for testing.

test control

The activity that develops and applies corrective actions to get a test project on track when it deviates from what was planned.

test data

Data needed for test execution.

test design

The activity that derives and specifies test cases from test conditions.

test execution

The activity that runs a test on a component or system producing actual results.

test implementation

The activity that prepares the testware needed for test execution based on test analysis and design.

test monitoring

The activity that checks the status of testing activities, identifies any variances from planned or expected, and reports status to stakeholders.

test object

The work product to be tested.

test objective

The purpose for testing.

test planning

The activity of establishing or updating a test plan.

test procedure

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 result

The consequence/outcome of the execution of a test.

testing

The process within the software development lifecycle that evaluates the quality of a component or system and related work products.

testware

Work products produced during the test process for use in planning, designing, executing, evaluating and reporting on testing.

validation

Confirmation by examination that a work product matches a stakeholder's needs.

verification

Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.

coverage

The degree to which specified coverage items are exercised by a test suite, expressed as a percentage.

debugging

The process of finding, analyzing and removing the causes of failures in a component or system.

defect

An imperfection or deficiency in a work product where it does not meet its requirements or specifications.

error

A human action that produces an incorrect result.

failure

An event in which a component or system does not perform a required function within specified limits.

quality

The degree to which a work product satisfies stated and implied needs of its stakeholders.

quality assurance

Activities focused on providing confidence that quality requirements will be fulfilled.

root cause

A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.

test analysis

The activity that identifies test conditions by analyzing the test basis.

test basis

The body of knowledge used as the basis for test analysis and design.

test case

A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.

test completion

The activity that makes testware available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to relevant stakeholders.

test condition

A testable aspect of a component or system identified as a basis for testing.

test control

The activity that develops and applies corrective actions to get a test project on track when it deviates from what was planned.

test data

Data needed for test execution.

test design

The activity that derives and specifies test cases from test conditions.

test execution

The activity that runs a test on a component or system producing actual results.

test implementation

The activity that prepares the testware needed for test execution based on test analysis and design.

test monitoring

The activity that checks the status of testing activities, identifies any variances from planned or expected, and reports status to stakeholders.

test object

The work product to be tested.

test objective

The purpose for testing.

test planning

The activity of establishing or updating a test plan.

test procedure

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 result

The consequence/outcome of the execution of a test.

testing

The process within the software development lifecycle that evaluates the quality of a component or system and related work products.

testware

Work products produced during the test process for use in planning, designing, executing, evaluating and reporting on testing.

validation

Confirmation by examination that a work product matches a stakeholder's needs.