[NEW] ISTQB Certified Tester Foundation Level - Agile Tester

Detailed Exam Domain Coverage

To ensure complete readiness for the official exam, these practice tests are mapped directly to the official syllabus structure. The questions are distributed across the four core domains to mirror the weight of the actual certification:

• Agile Fundamentals for Testers (20% of the exam)

  • Agile values and principles rooted in the Agile Manifesto.

  • Scrum framework fundamentals (understanding roles, events, and artifacts).

  • Kanban and Lean development concepts.

  • The structural and cultural differences between traditional testing and agile testing.

• Agile Testing Practices (30% of the exam)

  • Test-driven development (TDD), Behavior-driven development (BDD), and Acceptance test-driven development (ATDD).

  • Applying exploratory testing inside fast-paced sprints.

  • Continuous integration (CI) environments and automated testing pipelines.

  • Collaborative techniques including pair testing and mob testing.

• Test Planning and Management in Agile (25% of the exam)

  • Creating, executing, and maintaining lightweight test charters.

  • Working with story-level acceptance criteria and the Definition of Done (DoD).

  • Participating in sprint planning, backlog grooming, and agile test task estimation.

  • Applying risk-based testing principles and prioritization strategies in volatile environments.

• Agile Quality Metrics and Continuous Improvement (25% of the exam)

  • Interpreting agile metrics: Velocity, sprint burndown, and cumulative flow diagrams.

  • Tracking quality states through defect density, escape rates, and test automation coverage.

  • Contributing effectively to retrospectives for continuous testing process improvement.

  • Optimizing feedback loops and understanding the tester's role in delivering shippable increments.

Course Description

Earning the ISTQB® Certified Tester Foundation Level - Agile Tester (CTFL-AT) credential requires more than just skimming through the syllabus. The actual exam tests your ability to apply agile testing methodologies under time pressure, often presenting subtle, scenario-based questions where multiple answers seem plausible at first glance.

I designed this practice test course to bridge the gap between theoretical knowledge and exam-day reality. Instead of simple memorization drills, these original questions force you to analyze situations just like you would during the real test. Every question in this repository comes paired with a deep-dive explanation that clarifies the underlying agile principle, ensuring you understand the core mechanics rather than just memorizing a pattern.

A key differentiator of this course is the exhaustive breakdown of options. I do not just tell you which answer is right; I break down the incorrect options to show you exactly why they fail to meet the ISTQB criteria or where the distraction lies. This method helps eliminate confusion and sharpens your test-taking intuition. By exposing yourself to these realistic scenarios, you will identify your specific weak points across the four exam domains and fix them before sitting for the paid certification.

Practice Questions Preview

Below is a sample of the types of scenario-focused questions included in this course, demonstrating the thorough breakdowns you will receive for every single question.

Question 1: Agile Fundamentals for Testers

Scenario: A software organization is transitioning from a traditional V-model lifecycle to the Scrum framework. During the second sprint, a developer tells the tester that writing formal, multi-page test cases is a waste of time because the Agile Manifesto values "working software over comprehensive documentation." How should an agile tester best respond to this situation?

• A) Agree with the developer and stop writing all forms of test documentation immediately to speed up delivery.

• B) Explain that while working software is valued more, lightweight and valuable documentation—like test charters or acceptance criteria—is still necessary to support quality and collaboration.

• C) Insist on maintaining traditional, highly detailed test cases to ensure compliance with rigid organizational governance policies.

• D) Report the developer to the Scrum Master for violating the core principles of independent quality assurance.

• E) Suggest that the team skip testing altogether for the current sprint and focus exclusively on writing clean code.

• F) Demand that the Product Owner write all the test documentation instead so the tester can focus solely on manual execution.

Correct Answer: B

Explanations:

• Why Option B is correct: The Agile Manifesto states that while we value working software more, there is still value in the items on the right, including documentation. Agile testing emphasizes lightweight, purposeful documentation (like test charters, automation scripts, and user story criteria) that aids the whole team, rather than exhaustive, bureaucratic text.

• Why Option A is incorrect: Completely eliminating documentation is a misinterpretation of agile. Total lack of documentation causes regression issues, loss of tribal knowledge, and tracking confusion within the team.

• Why Option C is incorrect: Maintaining traditional, heavy, multi-page test cases directly contradicts the agile goal of agility, responsiveness, and minimizing waste. It introduces unnecessary overhead into a fast-paced sprint.

• Why Option D is incorrect: This is an adversarial, non-collaborative approach. Agile teams rely on open communication and collective ownership of quality, not immediate escalation over a conceptual disagreement.

• Why Option E is incorrect: Skipping testing violates the fundamental agile principle of delivering a high-quality, potentially shippable increment at the end of every sprint.

• Why Option F is incorrect: Documenting testing activities is a collaborative effort, but shifting the entire testing documentation burden onto the Product Owner is an inefficient use of roles and destroys cross-functional team dynamics.

Question 2: Agile Testing Practices

Scenario: Your cross-functional agile team wants to implement a practice where testers and developers collaborate closely at a single workstation to write test code and application code simultaneously. This is intended to improve feedback loops and share knowledge. Which practice does this scenario describe?

• A) Continuous Integration Pipeline Architecture

• B) Traditional Independent Acceptance Testing

• C) Pair Testing

• D) Behavior-Driven Development (BDD) Specification Workshops

• E) Static Analysis and Code Review Insulation

• F) Retrospective Process Refinement

Correct Answer: C

Explanations:

• Why Option C is correct: Pair testing involves two team members (frequently a tester and a developer, or two testers) working together at one workstation to test the software, share perspectives, and uncover defects rapidly while sharing technical and business knowledge.

• Why Option A is incorrect: Continuous Integration refers to the automated build and test process triggered when code is checked into a repository. It is a technical pipeline infrastructure, not a live, two-person collaborative practice.

• Why Option B is incorrect: Traditional independent testing typically happens in isolation, often in a separate phase or siloed department after development is complete, which is the exact opposite of this real-time collaboration.

• Why Option D is incorrect: BDD specification workshops (or the "Three Amigos" meetings) focus on defining requirements and examples before code is written, rather than sitting together at a single workstation writing code and executing tests simultaneously.

• Why Option E is incorrect: Static analysis is an automated tool-driven check of source code without running it. It does not describe active, collaborative human pair-work.

• Why Option F is incorrect: A retrospective is an event held at the end of a sprint to analyze past processes and plan improvements; it is not an active execution or coding practice.

Question 3: Agile Quality Metrics and Continuous Improvement

Scenario: Midway through a 14-day sprint, the team looks at the daily sprint burndown chart. The line showing "Remaining Work" has remained completely flat for five consecutive days, staying well above the ideal burn line. What is the most reasonable diagnostic conclusion for the tester to bring up?

• A) The automated regression suite has achieved maximum code coverage.

• B) The team's velocity has successfully doubled compared to the previous sprint.

• C) No remaining tasks are being marked as complete, indicating potential blockers, hidden complexity, or stalled progress.

• D) The defect density of the current software increment has dropped to zero.

• E) The cumulative flow diagram has automatically replaced the burndown chart metrics.

• F) The Product Owner has successfully added three new features to the sprint backlog.

Correct Answer: C

Explanations:

• Why Option C is correct: A flat line on a sprint burndown chart indicates that the estimated hours or story points of remaining work are not decreasing. This means tasks are stuck, unexpected roadblocks have appeared, or team members are not updating their task statuses.

• Why Option A is incorrect: Test automation coverage metrics are independent of a sprint burndown chart's day-to-day progress line. A flat line tells us nothing about code coverage.

• Why Option B is incorrect: A flat line indicates zero visible progress on remaining work, which would mean velocity is stalling or dropping, definitely not doubling.

• Why Option D is incorrect: Burndown charts track the volume of remaining work tasks, not the internal defect density or the overall cleanliness of the code.

• Why Option E is incorrect: A cumulative flow diagram is a completely separate metric chart used primarily in Kanban/Lean contexts to track work items in various states. One does not replace or alter the behavior of the other.

• Why Option F is incorrect: If a Product Owner adds features to an active sprint backlog without removing anything, the burndown line would spike upward, not remain flat.

What to Expect in This Course

• Welcome to the Mock Exam Practice Tests Academy to help you prepare for your ISTQB® Certified Tester Foundation Level - Agile Tester (CTFL-AT) Exam.

• You can retake the exams as many times as you want

• This is a huge original question bank

• You get support from me if you have questions

• Each question has a detailed explanation

• Mobile-compatible with the Udemy app

I hope that by now you're convinced! And there are a lot more questions inside the course.