Free ISTQB-AGILE sample questions

Correct answer: Present data showing a correlation between the sprint's last user story and a high number of interdependent components, suggesting a need for better dependency analysis during planning.

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.

Correct answers: Static code analysis checks.; Fast-running unit and component integration tests.

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.

Correct answer: Given I am viewing a report with 3 pages, when I click the 'Export to PDF' button, then a PDF file is downloaded that contains all 3 pages with the correct charts and data.

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.

Correct answer: False

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.

Correct answer: Propose a team agreement in the next retrospective that developers must run all unit and integration tests locally before committing their code.

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.

Correct answer: To act as a model to help teams ensure they have a balanced test strategy that includes different types of tests.

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.

Correct answer: As a user with multiple accounts, explore fund transfers between my own accounts to discover any inconsistencies in balance updates and transaction history, especially when network connectivity is interrupted.

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.

Correct answer: The team (testers, developers, and PO) failed to collaboratively define and review comprehensive acceptance criteria that covered all relevant scenarios, such as percentage-based discounts.

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.

Correct answer: Have the tester and the Product Owner explain the reasoning behind their high and low estimates to facilitate a discussion about the scope and complexity of the work.

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.

Correct answer: Given a registered user exists with the email '[email protected]', When the user requests a password reset for that email, Then an email with a unique reset link should be sent to '[email protected]'.

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.