CTFL-AT Sample Questions & Answers

Sprint Zero is a preparation phase before the first feature-developing sprint. From a testing viewpoint, its main purpose is to set up the foundation for successful testing throughout the project. This includes setting up test environments, selecting and configuring test automation tools, defining an initial test strategy, and performing initial risk analysis.

BDD is a collaborative process. The tester's key role is to bring a critical, quality-focused perspective. While developers focus on implementation and Product Owners on business value, the tester should think about what could go wrong. This involves proposing negative scenarios (e.g., 'When I enter an invalid password'), boundary conditions, and alternative user flows to ensure the acceptance criteria are comprehensive and robust.

Quadrant 4 is focused on technology-facing tests that critique the product, which includes non-functional tests like performance, load, stress, and scalability. Since the user story is about improving performance and resilience of a technical component (the database connection pool) without changing business-facing functionality, the primary testing effort (e.g., load testing, stress testing the connection limits) falls squarely within Q4.

This statement is true and captures the essence of the whole-team approach. In Agile, quality is not a separate phase or the sole responsibility of a QA department. Developers, testers, product owners, and business analysts all contribute to and are collectively responsible for building a quality product.

By insisting on clear, testable acceptance criteria, the tester is ensuring that the team knows precisely what constitutes 'working software' for that feature. Without this clarity, the team cannot definitively measure progress or declare the story complete. The tester's action directly supports the principle that tangible, working software is the ultimate goal and measure of success.

This approach is a common Agile anti-pattern that mimics a traditional waterfall model within a sprint. The primary goal of Agile testing is to provide rapid, continuous feedback. Delaying testing until the end of the sprint means that significant defects might only be discovered when there is little to no time left to fix them, jeopardizing the sprint goal.

The sprint burndown chart is specifically designed to track the amount of work remaining (on the y-axis) against time (on the x-axis) within an iteration. It provides a clear, visual representation of whether the team is on track to complete the sprint commitment.

The TDD cycle is: 1. Red: Write a failing test for a new function. 2. Green: Write the minimum amount of production code necessary to make the test pass. 3. Refactor: Clean up the code while ensuring the test still passes. Therefore, the production code is written during the 'Green' step.

By automatically building and running tests on every code check-in, CI helps catch regressions almost immediately.

A primary benefit of CI is the fast feedback loop; developers know within minutes if their change broke the build or failed tests.

A successful CI pipeline results in a working, tested build, ensuring that there is always a 'green' version of the software ready for deployment or further testing.

Agile principles emphasize early and frequent communication to prevent misunderstandings and rework. Given the high-risk nature of the feature (financial transactions, security), the most effective action is to address the gap in requirements immediately. By collaborating with the PO and developers, the testers can help define testable acceptance criteria for scenarios like invalid phone numbers, insufficient funds, transaction timeouts, and potential security exploits. This prevents the team from building a feature that is functionally correct but unsafe and incomplete.