CTFL-AT Certified Tester Foundation Level Agile Tester Questions and Answers

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 2.4 and 2.5:

"Due to frequent changes and short iterations, testers must be flexible and responsive. However, keeping up with pace can be a challenge."

Thus, Option D is correct — testers may struggle with rapid changes and short feedback loops, which is a known challenge in Agile.

Option A is false — testers still measure coverage and report defects .

Option B misrepresents TDD — developers typically write the unit tests in TDD.

Option C is incorrect — quality is a shared responsibility in Agile.

 A task management tool is a software application that helps agile teams plan, organize, and monitor their work. A task management tool typically allows the team to create, assign, prioritize, update, and track user stories, tests, and other tasks that are part of the agile project. A task management tool can also provide various views and reports to visualize the progress and status of the project, such as Kanban boards, burndown charts, velocity charts, etc.  Some examples of task management tools are Jira, Trello, Asana, and Monday.com 1 2 3 4 5 .  References : ISTQB® Foundation Level Agile Tester Syllabus, Section 2.1.1, page 13; ASTQB Agile Tester Certification Resources, Section 2.1.1, page 13.

According to the ISTQB Tester Foundation Level Agile Tester syllabus, acceptance criteria are a set of conditions that a user story must satisfy to be accepted by the customer or stakeholder. Acceptance criteria should be  testable , meaning that they can be verified by objective measurements or observations. Testable acceptance criteria should be  clear ,  unambiguous ,  complete , and  consistent . Therefore, option A is the best example for testable acceptance criteria, as it specifies a clear and measurable condition for the input value of the ID field. Option B is not a good example for testable acceptance criteria, as it is vague and does not define any specific condition or expectation for the interface to External System. Option C is not a good example for testable acceptance criteria, as it is incomplete and does not specify what the specific authorization level is or how it is determined. Option D is not a good example for testable acceptance criteria, as it is subjective and not measurable. What is clear and attractive for one user may not be for another.  References : ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.1, page 7; ISTQB Tester Foundation Level Agile Tester syllabus, section 1.1.2, page 8; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.1, page 23; ISTQB Tester Foundation Level Agile Tester syllabus, section 3.1.2, page 24.

3of30

 Agile software development is a term that encompasses a group of software development methodologies that are based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. Agile methods promote adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourage rapid and flexible response to change. Some examples of agile methods are Scrum, Extreme Programming (XP), Kanban, and Lean Software Development.  References :

: ISTQB® Foundation Level Agile Tester Syllabus, Version 2014, Section 1.1.1

: ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 1, Section 1.1.1

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 4.3 Test Automation and Continuous Integration , it states:

"Automated tests help detect regression defects quickly and can be run frequently during development, thus reducing regression risk."

So, Option D is correct — test automation supports regression testing within iterations, making it an essential Agile practice.

Option A is false — automated unit tests are designed to be fast and are ideally run with every check-in.

Option B is incorrect — more code changes increase , not reduce, regression risk.

Option C is incorrect — technical debt can still exist with automation if the automation is poorly designed or not maintained.

Comprehensive and Detailed Explanation From Exact Extract:

From the CTFL-AT Syllabus v4.0 , Section 1.3 The Whole-Team Approach , it states:

"The whole-team approach involves all team members (including developers, testers, and business representatives) working together as a team, sharing responsibility for the quality of the product."

It also says:

"In Agile projects, the whole-team approach promotes collaboration and communication across roles to achieve common goals, including quality assurance."

Thus, Option B is correct, as it captures the collaborative nature and shared responsibility that the whole-team approach aims to foster.

Option A refers to Planning Poker or relative estimation , not directly the whole-team concept.

Option C describes the "Three Cs" (Card, Conversation, Confirmation) model of user stories, not the whole-team approach specifically.

Option D misinterprets Agile; while team members are encouraged to be cross-functional , deep expertise is still valued, and "generalist only" is not a requirement of the whole-team approach.

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 3.2 Test-Driven Development , and Section 3.4 Testing Quadrants :

"TDD focuses on writing unit tests before code is implemented. These are technology-facing tests that support the team and are categorized under Q1."

Therefore, Option D is correct.

Option A involves performance/security testing.

Option B and C involve business-facing tests , not applicable to TDD.

The tester within an Agile team is not responsible for ensuring all project status meetings are held according to the plan. This is typically a task for the Scrum Master, who facilitates the meetings and ensures that the team follows the Agile principles and practices. The tester within an Agile team is responsible for ensuring the appropriate testing tasks are scheduled during iteration planning, suggesting improvements in team retrospectives, and working with business stakeholders to clarify requirements.  These are all tasks that contribute to the quality of the software and the testing process, as well as the collaboration and communication within the team and with the customers.  References:  ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.1, page 17 1 ; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.1-1, page 8 2

 Release planning is a process of defining the scope and timeline for an iterative or incremental product development project.  It is used in agile or hybrid projects where a mid- to long-term planning of the product or system development or integration is required 1 2 . Release planning involves the following activities:

Identifying testable user stories with acceptance criteria. User stories are short descriptions of the features or functionalities that the customer or user wants from the product. Acceptance criteria are the conditions that must be met for the user story to be considered done and acceptable.  Identifying testable user stories with acceptance criteria helps to define the scope and quality of the release 1 3 .

Prioritizing the user stories. User stories are prioritized based on the value they deliver to the customer or user, as well as the dependencies, risks, and costs associated with them.  Prioritizing the user stories helps to determine the order and frequency of the releases 1 3 .

Performing high level estimation for the release. High level estimation is a technique to estimate the effort, time, and resources needed to complete the user stories in the release. High level estimation can be done using various methods, such as analogy, expert judgment, planning poker, etc.  Performing high level estimation for the release helps to set realistic and achievable goals and deadlines 1 3 .

Therefore, activities 1, 3 and 6 are done in release planning.  Activities 2, 4 and 5 are done in iteration planning, which is a more detailed and short-term planning of the work to be done in each iteration or sprint 1 3 .  References :  1 : ISTQB® Foundation Level Agile Tester Syllabus, Section 2.2, Fundamental Agile Testing Principles, Practices and Processes 1 ;  2 : Agile Release Planning in Hybrid and Agile Projects 4 ;  3 : How to Create an Agile Release Plan 5

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 3.1 Exploratory Testing :

"Exploratory testing benefits from tools that record tester activity, allowing the tester to reproduce and document issues found during unscripted testing sessions."

Option D is correct — activity capture tools help testers log, replay, and report findings effectively in exploratory sessions.

Option A is for test data preparation, not reporting.

Option B is related to integration, not exploratory testing.

Option C helps track tasks but lacks session capture features.

Comprehensive and Detailed Explanation From Exact Extract:

From the CTFL-AT Syllabus v4.0 , Section 5.1, it states:

"The team uses the retrospective to review how they worked during the iteration, including planning accuracy and team collaboration, and to identify actionable improvements."

Thus, Option D is correct — retrospectives help reflect on iteration planning accuracy, team dynamics , and efficiency to improve future iterations.

Option A is incorrect — retrospectives aim to focus on what the team can improve , not just on external hindrances.

Option B is false — Agile retrospectives require follow-up , often in the form of action items tracked in the next iteration.

Option C is incorrect — Product Owner and possibly others may contribute, depending on team context.

Comprehensive and Detailed Explanation From Exact Extract:

From the CTFL-AT Syllabus v4.0 , Section 5.1 Agile Retrospectives and Process Improvement , it states:

"Retrospectives are used to reflect on what went well and what could be improved. They should include qualitative insights and quantitative measures such as velocity, burndown charts, and number of stories completed."

Therefore, Option C is correct, as using metrics to support process improvement is a recommended best practice in retrospectives.

Option A is incorrect — retrospectives should include what went well , not just negatives.

Option B is inaccurate — not all improvements must be implemented immediately; they are prioritized and planned based on capacity and impact.

Option D is false — retrospectives are held at the end of every iteration , regardless of story points completed.

A whole-team approach is a way of working in agile projects where all team members share the responsibility for delivering high-quality software that meets the customer’s needs. This means that testers, developers, business analysts, and other roles collaborate closely throughout the project lifecycle, and use their different skills and perspectives to contribute to the quality of the product. A benefit of this approach is that it enables the team to leverage the various skill sets within the team to the benefit of the project, such as testing skills, coding skills, domain knowledge, user experience, etc.  This can lead to faster feedback, better communication, higher productivity, and more innovation.  References : ISTQB® Foundation Level Agile Tester Syllabus 1 , Section 1.1.1, page 7; ASTQB Agile Tester Certification Resources, Section 1.1.1, page 7.

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 4.3 Test Automation and Continuous Integration , and the ISTQB Glossary:

"Test automation involves using software to execute tests, compare actual outcomes to expected outcomes, and report the results automatically."

Thus, Option A correctly defines test execution automation .

Option B describes session-based testing , not automation.

Option C describes Test-Driven Development (TDD) .

Option D refers to test execution , not specifically automation.

Comprehensive and Detailed Explanation From Exact Extract:

From the CTFL-AT Syllabus v4.0 , Section 2.1 User Stories and Acceptance Criteria , it states:

"Acceptance criteria are defined collaboratively and refined during the conversation to ensure mutual understanding. They may be added or updated as new insights emerge."

This supports Option D , which reflects how acceptance criteria evolve during conversations — a key component of the "Card, Conversation, Confirmation" model.

Option A is incorrect — the user story is testable , especially with the acceptance criterion.

Option B is false — the story provides clear user value (printed hard copy for daily records).

Option C is misleading — the Given-When-Then format supports discussions; it doesn’t replace them.

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 3.1 Testing Techniques and Agile , it states:

"Decision table testing is useful when the outcome depends on combinations of inputs or rules."

In this case, different reimbursement percentages are determined based on types of visits and subtypes , making Option A (Decision Table Testing) the ideal technique.

Option B focuses on single input ranges , less suitable here.

Option C suits end-to-end scenarios but not logic-driven calculations.

Option D applies to state-based systems , which this is not.

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 2.2 Release and Iteration Planning , it describes Planning Poker as:

"Planning Poker involves group discussion, especially from the highest and lowest estimators, to ensure that different perspectives and assumptions are aligned, which leads to more accurate and shared understanding of the effort involved."

Thus, Option C is correct — Team B uses discussion-based estimation , which is a core benefit of Planning Poker.

Option A is speculative — we cannot know the actual effort difference.

Option B is incorrect — convergence without discussion may indicate lack of engagement or pressure to agree .

Option D is false — Planning Poker is not based on averaging , but on consensus .

Comprehensive and Detailed Explanation From Exact Extract:

From the ISTQB CTFL-AT Syllabus v4.0 , Section 1.2 The Fundamentals of Agile Software Development , Kanban is explained as:

"In Kanban, work is visualized using a board that shows tasks in various states of progress. The transparency of the workflow helps teams identify bottlenecks, improve flow, and collaborate effectively."

This directly supports Option C , where Kanban boards are used for visualizing active tasks — increasing transparency and progress visibility .

Let’s clarify the other options:

Option A : The five values listed — communication, simplicity, feedback, courage, and respect — are associated with Extreme Programming (XP) , not Kanban.

Option B : Scrum does not prescribe specific testing techniques , but it also does not dictate how development must be done , which makes this a trick answer that’s partially true but not complete or precise enough to be correct.

Option D : The roles are incorrectly named . The correct Scrum roles are:

Product Owner ,

Scrum Master ,

Developers (Development Team is no longer a formal term post-2020 Scrum Guide)

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 2.1 Acceptance Criteria and Testability , acceptance tests must be directly related to the new functionality described in the user story.

Option D is correct — it validates the new feature of paying via smartcard credit, specifically handling edge cases (e.g., zero credit).

Option A is incorrect — payment should fail with insufficient credit.

Option B introduces requirements not mentioned in the story.

Option C tests credit card logic , not the new smartcard functionality.

 Early and frequent feedback is one of the core values of Agile development. It helps the Agile team to deliver features with the highest business value first, to discover and resolve quality problems as soon as possible, to provide information on the team’s productivity and progress, and to ensure that the product meets the customer’s expectations and needs. However, early feedback does not necessarily decrease the amount of time needed for system testing, as system testing is still an important activity in Agile projects to verify the integration and functionality of the whole system.  Early feedback may reduce the number of defects found in system testing, but it does not eliminate the need for system testing.  References : ISTQB Foundation Level Agile Tester Extension Syllabus 1 , page 10; ISTQB Agile Tester Sample Exam 2 , question 11.

Comprehensive and Detailed Explanation From Exact Extract:

From the CTFL-AT Syllabus v4.0 , Section 4.2 Continuous Integration , it states:

"Continuous integration involves integrating code into a shared repository several times a day. Each integration is verified by an automated build and automated tests."

Hence, Option D — at least once a day — correctly reflects best practice in continuous integration.

Option A (once per iteration) and B , C are far too infrequent to meet the goals of CI.

The objective is to detect integration issues early and often , which is only achievable through daily (or more frequent) integrations.