ISTQB CTAL-TA Syllabus v4.0 Focused Study Glossary

Comprehensive vocabulary flashcards covering chapter keyword terms and syllabus-specific domain vocabulary from the ISTQB CTAL-TA Syllabus v4.0 focused study glossary.

High-level test case

A test case with abstract preconditions, input data, expected results, postconditions, and actions (where applicable).

Keyword

A phrase that represents specific actions to be performed during test execution.

Keyword-driven testing

A test automation approach in which test scripts contain keywords and supporting files contain scripts that implement those keywords.

Low-level test case

A test case with concrete values for preconditions, input data, expected results, postconditions, and a detailed description of actions (where applicable).

Software development lifecycle

The activities performed at each phase in software development, and how they relate to one another logically and chronologically.

Test analysis

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

Test analyst

A person responsible for test analysis, test design, test implementation, and test execution, focusing on non-technical aspects of software.

Test case

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

Test condition

A testable aspect of a component or system that is intended to be tested.

Test data

Data needed for test execution.

Test design

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

Test environment

An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to perform a test.

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.

Test oracle

A source to determine an expected result.

Test script

A sequence of instructions for the execution of a test.

Testware

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

Impact analysis

The identification of all work products affected by a change, including an estimate of the resources needed to accomplish the change.

Product risk

A risk that impacts the quality of a product.

Regression testing

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

Risk analysis

The overall process of risk identification and risk assessment.

Risk assessment

The process of examining identified risks and determining the risk level.

Risk control

The overall process of risk mitigation and risk monitoring.

Risk identification

The process of finding, recognizing and describing risks.

Risk mitigation

The process through which decisions are reached and protective measures are implemented for reducing or maintaining risks to specified levels.

Risk monitoring

The activity that checks and reports the status of known risks to stakeholders.

Risk-based testing

A test approach in which the management, selection, prioritization, and use of test activities and resources are based on corresponding risk types and risk levels.

Checklist-based testing

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

Behavior-based test technique

A black-box test technique in which test conditions are model elements of the state-dependent behavior of a test object.

Combinatorial testing

A black-box test technique in which test conditions are specific combinations of values of several parameters.

Crowd testing

A test approach in which testing is distributed to a large group of testers.

CRUD testing

A black-box test technique in which test conditions are operations of the types create, read, update, and delete for an entity.

Data-based test technique

A test technique in which test conditions are model elements of the test object data.

Decision table testing

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

Domain testing

A black-box test technique in which test conditions are points on, near to, inside or outside the boundaries of different equivalence partitions of the input value domain.

Equivalence partition

A subset of a value domain for which a component or system is expected to treat all values the same based on the specification.

Experience-based testing

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

Metamorphic relation

A description of how a change to an input for a test case affects an expected result based on the required behavior of a test item.

Metamorphic testing

A test technique in which test conditions are metamorphic relations.

Random testing

A black-box test technique in which input values are randomly generated.

Rule-based test technique

A black-box test technique in which test conditions are model elements of the state-independent behavior rules of a test object.

Scenario-based testing

A black-box test technique in which test conditions are sequences of interactions between external actors and the test item.

Session-based testing

A test approach in which test activities are planned as test sessions.

State transition testing

A black-box test technique in which test conditions are state transitions or sequences of them.

Test charter

A mission statement that guides an exploratory test session.

Adaptability

The degree to which a component or system can be adapted to various or evolving hardware, software, or other operational or usage environments.

Compatibility

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.

Flexibility

The degree to which a component or system can be adapted to changes in its requirements, contexts of use, or system environment.

Functional appropriateness

The degree to which the functions facilitate the accomplishment of specified tasks and objectives.

Functional completeness

The degree to which the set of functions covers all the specified tasks and user objectives.

Functional correctness

The degree to which a component or system provides the correct results with the needed degree of precision.

Functional suitability

The degree to which a component or system provides functions that meet stated and implied needs when used under specified conditions.

Functional testing

A test type to determine the functional suitability of a test object.

Installability

The degree to which a component or system can be successfully installed and/or uninstalled in a specified environment.

Interaction capability

The degree to which a component or system can exchange information via the user interface with its specified users to complete an intended task.

Interoperability

The degree to which two or more components or systems can exchange information and use the information that has been exchanged.

Usability

The degree to which a component or system can be used by specified users to achieve specified goals in a specified context of use.

User experience

A person's perceptions and responses resulting from the use or anticipated use of a software product.

Ad hoc reviewing

A review technique performed informally without a structured process.

Checklist-based reviewing

A review technique guided by a list of questions or required attributes.

Defect prevention

Measures that reduce the likelihood of recurrence of defects in work products and limit the propagation of defects in subsequent work products.

Model-based testing

Testing based on or involving models.

Perspective-based reading

A type of role-based reviewing that uses checklists and involves the creation of prototype deliverables.

Review technique

A procedure used to perform a review.

Role-based reviewing

A review technique in which a work product is evaluated from the perspective of different stakeholder roles.

Root cause analysis

The process used to identify the root cause of a defect.

Scenario-based reviewing

A review technique in which a work product is evaluated to determine its ability to address specific scenarios.

Test result

The status of the execution of a test.

CRUD matrix

A matrix that indicates the action types of the functions on the entities within a system.

Data semantics

The meaning and interpretation of data.

Five whys technique

An iterative questioning technique used to determine a root cause by asking “why?” repeatedly, each time using the previous answer to guide the next question.

Pareto analysis

An approach to identify problem areas or tasks that will have the biggest payoff.

User journey map

A visualization showing the steps a user takes in a process to accomplish a goal.

User research

Learning about users’ needs and thought processes by studying how they perform tasks, observing interactions, or analyzing and interpreting data.