Covers agile software development fundamentals and approaches, how agile testing differs from traditional testing and the tester's role on a team, and agile testing methods.
20 free sample questions239 in the full practice test Other version: CTFL-AT(203)
Agile Software Development · FA-1.2.3 Understand how retrospectives can be used as a mechanism for process improvement in Agile projects
During a sprint retrospective, a tester observes that the team consistently fails to complete the last user story in each sprint. The burndown chart shows a pattern where progress is steady for the first week, but flatlines in the second week. Which of the following is the most productive contribution the tester can make to the discussion?
Answer and explanation
Correct answer: C
The most productive contribution is data-driven and focuses on process improvement. By analyzing the characteristics of the failed user stories, the tester provides concrete evidence that can lead to a specific, actionable improvement in the planning process. Blaming is counterproductive. Suggesting a velocity reduction is a symptom, not a root cause. Insisting on more testing time without identifying the root cause is not a collaborative solution.
Q2Question 2
IntermediateMultiple answers
Agile Software Development · FA-1.2.4 Understand the use and purpose of continuous integration
A new Agile team is setting up their continuous integration (CI) pipeline. A debate arises about which tests should be included in the primary CI loop that runs on every code commit. As the team's tester, which TWO of the following should you advocate for including in this frequent, on-commit build? (Select TWO)
Answer and explanation
Correct answers: A, C
The primary goal of the on-commit CI loop is to provide extremely fast feedback to developers. Therefore, only the quickest checks should be included. Static code analysis and fast-running unit/component tests fit this requirement. Full end-to-end UI tests and performance tests are typically too slow and are run less frequently (e.g., nightly). Manual exploratory testing is not part of an automated CI pipeline.
Q3Question 3
Intermediate
Agile Software Development · FA-1.2.2 Write testable user stories in collaboration with developers and business representatives
You are a tester on a Scrum team. During sprint planning, the Product Owner presents the following user story: 'As a premium user, I want to export my report to PDF, so I can share it with my manager.' Which of the following is the BEST example of a well-formed, testable acceptance criterion for this story?
Answer and explanation
Correct answer: D
A well-formed acceptance criterion is specific, testable, and often follows a format like Given-When-Then. It describes an observable outcome from a user's perspective. Option D clearly defines the context, action, and expected result, making it unambiguous and easy to verify. The other options are too vague ('work correctly'), incomplete, or describe an internal quality metric (code coverage) rather than user-facing behavior.
Q4Question 4
Beginner
Fundamental Agile Testing Principles, Practices, and Processes · FA-2.1.2 Describe how development and testing activities are integrated in Agile projects
True or False: In an Agile project, the 'Definition of Done' (DoD) for a user story should be established by the test team to ensure quality standards are met.
Answer and explanation
Correct answer: B
The 'Definition of Done' is a shared understanding of what it means for work to be complete. According to the whole-team approach, the DoD is created and agreed upon by the entire team, including developers, testers, and the product owner, not dictated by a single group.
Q5Question 5
Intermediate
Fundamental Agile Testing Principles, Practices, and Processes · FA-2.3.2 Understand the role of a tester within an Agile team
A tester on an Agile team notices that developers are frequently checking in code that breaks the build in the continuous integration system. This is causing delays for the entire team. How should the tester address this issue?
Answer and explanation
Correct answer: C
The role of an Agile tester includes coaching the team on quality. The most collaborative and effective approach is to facilitate a team-level solution. Proposing a new working agreement during a retrospective empowers the team to solve its own problem and reinforces the principle of collective ownership of quality and process. Reporting or creating unilateral rules goes against Agile principles of self-organizing teams.
Q6Question 6
Beginner
Agile Testing Methods, Techniques, and Tools · FA-3.1.3 Summarize the testing quadrants and their relationships with testing levels and testing types
Which of the following BEST describes the primary purpose of the Agile Testing Quadrants?
Answer and explanation
Correct answer: B
The Agile Testing Quadrants are a heuristic or model, not a rigid process. Their purpose is to guide a team in thinking about the different types and purposes of tests needed to achieve quality. It helps ensure that the team doesn't forget important test types, such as non-functional or exploratory tests, by providing a framework for discussion and planning.
Q7Question 7
Advanced
Agile Testing Methods, Techniques, and Tools · FA-3.3.5 Perform exploratory testing to support the testing of an Agile project
A team is developing a mobile banking application. For the 'fund transfer' user story, they need to conduct exploratory testing. Which of the following represents the MOST effective test charter for a 60-minute exploratory test session?
Answer and explanation
Correct answer: C
An effective test charter is specific and provides a clear mission. It defines the target (fund transfers between own accounts), the actor (user with multiple accounts), and the risks to investigate (inconsistencies, network interruptions). The other options are too generic and do not provide sufficient guidance for a focused and productive exploratory testing session.
Q8Question 8
Advanced
Agile Software Development · FA-1.1.2 Understand the advantages of the whole-team approach
Case Study: A retail company, 'ShopFast', has adopted Scrum for its new e-commerce platform. The team consists of 5 developers, 2 testers, 1 product owner, and 1 scrum master. In sprint 3, the team worked on a user story to implement a new discount coupon feature.
During the sprint review, the product owner applies a 15% discount coupon, and the final price is calculated incorrectly. A developer investigates and finds that the logic for percentage-based calculations was flawed. The team's 'Definition of Done' includes 'Unit tests passed with 85% code coverage' and 'All acceptance criteria manually verified by a tester'. The acceptance criteria for the story did not specify tests for percentage-based discounts, only for fixed-amount discounts.
Based on the whole-team approach to quality, what was the most significant failure that led to this defect escaping to the sprint review?
Answer and explanation
Correct answer: C
The core principle of the whole-team approach is shared responsibility for quality, which begins with a shared understanding of the requirements. The root cause of the defect was the gap in the acceptance criteria. This gap indicates a failure in the collaborative process between the PO, developers, and testers to explore the user story fully and define what 'done' means for all scenarios. While developer testing and tester exploration are important, they are guided by the acceptance criteria. The failure to create comprehensive criteria is the primary breakdown in the whole-team approach.
Q9Question 9
Intermediate
Agile Testing Methods, Techniques, and Tools · FA-3.2.2 Estimate testing effort based on iteration content and quality risks
In planning poker, the team is estimating a user story. The estimates revealed are: Product Owner (3), Developer 1 (8), Developer 2 (5), Tester (13). What is the most appropriate next step for the team?
Answer and explanation
Correct answer: B
The primary purpose of planning poker is not just to get a number, but to create a shared understanding of the work involved. A wide divergence in estimates, especially between the highest and lowest, indicates a difference in understanding. The next step should always be a discussion, led by those with the outlier estimates, to uncover hidden complexities, risks, or assumptions. The PO's vote is often considered input but not part of the final development team estimate, but their perspective on the low score is valuable. The tester's high estimate likely reveals testing complexities the developers haven't considered.
Q10Question 10
Intermediate
Agile Testing Methods, Techniques, and Tools · FA-3.3.3 Given a user story, write acceptance test-driven development test cases
A team is using Acceptance Test-Driven Development (ATDD). Given the user story 'As a user, I want to be able to reset my password if I forget it', which of the following represents a valid acceptance test in the Gherkin (Given-When-Then) format?
Answer and explanation
Correct answer: C
This option correctly uses the Given-When-Then structure to define a clear, unambiguous, and testable scenario. 'Given' sets the precondition, 'When' describes the action or event, and 'Then' specifies the expected outcome. The other options are either simple test descriptions or incomplete Gherkin syntax.
Register free for 10 more questions
Or unlock all 239 ISTQB-AGILE questions with explanations, timed mode and flashcards.