ISTQB CTAL-TA Release-Notes v3.1.0
ISTQB CTAL-TA Release-Notes v3.1.0
ISTQB CTAL-TA Release-Notes v3.1.0
Release Notes
This version is a minor update, because it has less than or equal to 5% changes of Learning Objectives, as
described in section 3.6.1 in ISTQB® Accreditation Process, version 2.00 document. Specifically, CTAL-TA has
30 learning objectives, so only one of them (TA-3.2.3) is impacted by this update. Change requests that would
impact other learning objectives have been postponed to the next major update.
A minor update does not require re-accreditation of training providers, but accredited training providers shall
confirm to their accreditation body that they have updated the training material accordingly.
The new version v3.1.0 of the syllabus comes into effect on the launch date of March 2nd, 2021
All ISTQB® Member Boards which currently provide the CTAL-TA Syllabus in English must:
All ISTQB® Member Boards which currently provide exams in the CTAL-TA Syllabus version 2019 in English
must ensure that all exam questions are consistent with the CTAL-TA Syllabus version v3.1.0 no later than 6
months after the launch date.
All ISTQB® Member Boards which currently provide CTAL-TA Syllabus version 2019 in their local language
must:
1) retire their old CTAL-TA Syllabus version 2019 translated to their local language
2) and either provide an updated / new translation of CTAL-TA Syllabus version v3.1.0 in their local
language
3) or only use the English version of the CTAL-TA Syllabus version v3.1.0 in their market no later than 9
months after the launch date.
All ISTQB® Member Boards which currently provide exams for the CTAL-TA Syllabus version 2019 in their
local language must ensure that all exam questions are consistent with the CTAL-TA Syllabus version v3.1.0
no later than 9 months after the launch date.
The effect of this rule is that there will be no further activity at any ISTQB® Member Board regarding the
previous 2019 version of the Syllabus from 6 months after the launch date in English, and from 9 months
after the launch date in non-English.
• Chapter 1:
o Section 1.2 (Testing in the Software Development Lifecycle): Wording improvements.
o Section 1.5 (Test Analysis): Activities aligned with the current CTFL test process.
• Chapter 2:
o List of keywords: “risk level” removed.
o Section 2.3 (Risk Assessment): Last two paragraphs on risk scale and risk level rating
rephrased.
• Chapter 3:
o Various wording improvements;
o Section 3.2.1 (Equivalence Partitioning):
Removed the discussion of continuous and discrete value ranges because it does not
add much value.
Extended the discussion from one single parameter to multiple parameters, to better
cover the learning objective.
o Section 3.2.2 (Boundary Value Analysis): Examples improved.
o Section 3.2.3 (Decision Table Testing): Section completely re-written.
Aligned with the standard OMG-DMN Chapter 8;
Emphasis on:
• Limited-entry vs. extended-entry decision tables;
• Differentiating between test conditions (the rules) and test cases;
• Collapsed decision tables (as promised in CTFL);
Removed the coverage of individual condition outcomes which has been introduced
in the 2019 version.
o Section 3.2.4 (State Transition Testing):
N-switch coverage explained more clearly;
Defect type “Wrong guard conditions” added.
Section 3.2.7 (Use Case Testing): Details aligned with the current OMG-UML standard
o
(version 2.5.1)
• Chapter 4:
o Various wording improvements;
o Section 4.2.3 (Functional Completeness Testing): “high-level business cases” replaced with
“high-level business processes”
o Section 4.2.5 (Usability Evaluation): The definitions of the sub-characteristics of usability are
replaced with a reference to the Glossary.
• Chapter 5:
o Section 5.2.1 (Requirement Reviews): List item “Priority of each requirement” added.
• Chapter 6:
o Minor wording improvements.
• Chapter 7 References:
o Standards [OMG-UML] and [OMG-DMN] added;
o References to ISTQB® and IREB documents updated;
o The original paper of Chow (1978) on N-Switch coverage added;
o Recent textbook of Forgács and Kovács (2019) on test design added.
• General:
o The following terms have been replaced with their correct Glossary equivalent or the
preferred term in CTFL:
“Agile projects” and other agile-related expressions replaced with “Agile software
development”;
“appropriateness” replaced with “functional appropriateness” wherever the quality
characteristic is meant;
“correctness” replaced with “functional correctness” wherever the quality
characteristic is meant;
“equivalence class” replaced with “equivalence partition”;
“functionality” replaced with “functional suitability” wherever the quality
characteristic is meant;
“keyword-driven automation” replaced with “keyword-driven testing”
“levels of testing” replaced with “test levels”;
“test coverage” as well as “testing coverage” replaced with “coverage”;
“testing activities” replaced with “test activities”;
“testing effort” replaced with “test effort”;
Matthias Hamburg