ISTQB CTFL-AT Certified Tester Foundation Level Agile Tester Exam Dumps and Practice Test Questions Set 5 Q81-100

Visit here for our full ISTQB CTFL-AT exam dumps and practice test questions.

Question 81: 

Which Agile practice focuses on small, iterative deliveries of working software?

A) Waterfall
B) Incremental Delivery
C) Big Bang Release
D) Phase Gate

Answer: B) Incremental Delivery

Explanation:

Waterfall is a traditional software development methodology that follows a sequential approach, where each phase must be completed before the next begins. In Waterfall, requirements are collected upfront, design and development occur in distinct stages, and the product is only delivered at the end of the project. This method does not align with Agile principles because it lacks flexibility, limits early stakeholder feedback, and increases the risk of late defect discovery. Since Waterfall focuses on a single final release, it cannot provide iterative, incremental delivery of working software that Agile emphasizes.

Phase Gate, also known as stage-gate methodology, is another sequential approach commonly used in project management. In Phase Gate, work progresses through defined gates or checkpoints, and advancement depends on meeting specific criteria at each stage. While it introduces structured review points, it is still linear in nature and does not promote small, iterative releases. This approach delays feedback from actual users and prevents the development team from responding quickly to changes, which is contrary to the Agile philosophy of incremental delivery.

Big Bang Release is a model where the entire product is developed and delivered in a single release. While this approach may work for small projects, it is risky for larger initiatives because there is no opportunity to test assumptions, gather early feedback, or make iterative improvements. Any issues discovered at the final stage can lead to significant rework, wasted effort, and unsatisfied stakeholders. This is essentially the opposite of incremental delivery, which emphasizes producing usable, testable increments throughout the project.

Incremental Delivery is the correct choice because it embodies Agile’s core principle of delivering small, functional pieces of software regularly. By releasing increments, teams can validate features early, gather stakeholder feedback, and continuously improve the product. Each increment is potentially shippable, reduces the risk of large-scale failure, and ensures the project stays aligned with evolving requirements. Incremental delivery enables teams to maintain momentum, learn from previous iterations, and adapt their planning as new information emerges, which is a defining characteristic of Agile practices.

Question 82: 

Which of the following is a primary benefit of automated regression testing in Agile?

A) Replaces exploratory testing
B) Provides fast, repeatable verification of existing functionality
C) Eliminates need for unit testing
D) Reduces the need for sprint planning

Answer: B) Provides fast, repeatable verification of existing functionality

Explanation:

Replaces exploratory testing is incorrect because automated regression testing and exploratory testing serve different purposes. Exploratory testing relies on the creativity and intuition of testers to discover unexpected defects, often in areas that automated tests cannot easily cover. Automated regression testing does not replace the need for exploratory testing; instead, it complements it by handling repetitive checks efficiently. Ignoring exploratory testing would leave gaps in coverage, especially when testing complex or unpredictable scenarios.

Eliminates need for unit testing is also incorrect. Unit testing focuses on verifying individual components or modules of code to ensure they function correctly in isolation. Automated regression testing validates that existing functionality continues to work correctly after changes, but it does not replace the granularity and early detection benefits of unit testing. Unit tests are essential for developers to catch issues early in the development process, while regression tests ensure that these components remain reliable after integration or system-level changes.

Reduces the need for sprint planning is inaccurate because regression testing does not replace the planning process. Sprint planning is focused on prioritizing work, defining goals, and estimating effort for the upcoming sprint. Regression testing ensures that completed functionality remains stable, but it does not influence how work is selected or organized in the sprint backlog. Planning remains a human-driven activity based on project needs and priorities, independent of test automation.

Provides fast, repeatable verification of existing functionality is correct because automated regression testing is designed to execute predefined test cases consistently and quickly, ensuring that previously working features remain intact after changes. In Agile environments, where frequent iterations and continuous integration are common, automated regression testing enables teams to detect defects early, reduce manual testing effort, and maintain the product’s stability. This rapid feedback supports continuous delivery and helps the team maintain a potentially shippable product increment after each sprint, which is vital for sustaining Agile workflows.

Question 83: 

Which Agile artifact shows work remaining versus time in a sprint?

A) Product Backlog
B) Burndown Chart
C) Sprint Backlog
D) Definition of Done

Answer: B) Burndown Chart

Explanation:

Product Backlog is a prioritized list of all desired features, enhancements, and bug fixes for a product. While it is essential for planning and managing work, it does not show progress over time or the remaining work for a specific sprint. The backlog is more strategic in nature, capturing the full scope of the project rather than visualizing daily sprint progress, which makes it unsuitable as a tool for monitoring work completed versus remaining work during an iteration.

Sprint Backlog represents the subset of product backlog items selected for implementation in the current sprint, along with the plan for completing them. While the sprint backlog details what the team is working on, it does not inherently visualize progress over time. It provides task-level granularity but lacks the graphical representation that helps teams quickly assess whether they are on track to complete the sprint objectives.

Definition of Done establishes the criteria that must be met for a product backlog item or increment to be considered complete. It ensures quality and clarity for work items, promoting shared understanding among the team. However, it is not a tracking or visualization tool and does not provide information on remaining work or time progression during a sprint.

Burndown Chart is correct because it graphically represents the remaining work against the sprint timeline. Teams can quickly see trends, identify bottlenecks, and make necessary adjustments to stay on track. By plotting remaining effort versus time, it enhances transparency, enables proactive risk management, and provides a visual mechanism for both the team and stakeholders to monitor progress. This artifact supports Agile principles of inspection and adaptation, making it an indispensable tool for iterative development.

Question 84: 

Which Agile testing approach uses tester creativity and simultaneous learning, test design, and execution?

A) Unit Testing
B) Exploratory Testing
C) Smoke Testing
D) Load Testing

Answer: B) Exploratory Testing

Explanation:

Unit Testing is a testing approach that focuses on verifying individual components or modules of code. It is typically automated and requires predefined inputs and expected outcomes. While essential for ensuring correctness at a granular level, unit testing is highly structured and does not involve the creative, adaptive problem-solving that characterizes exploratory testing.

Smoke Testing, also known as build verification testing, checks whether basic functionality of the system works after a new build. It is a quick, high-level validation meant to catch major failures early. Smoke testing is scripted and routine, focusing on the presence or absence of major issues, rather than engaging in the creative, adaptive learning and testing process associated with exploratory testing.

Load Testing evaluates system performance under heavy usage or stress conditions. It helps identify bottlenecks, performance limits, and scalability issues. Load testing is usually automated and highly structured, focused on performance metrics rather than functional defects discovered through creative exploration of the system.

Exploratory Testing is correct because it emphasizes simultaneous learning, test design, and execution. Testers interact with the software dynamically, exploring potential edge cases and unanticipated behavior. This approach complements automated testing by identifying defects that scripted tests may miss. In Agile, where requirements can evolve rapidly and early feedback is critical, exploratory testing provides rapid insights, uncovers hidden issues, and supports continuous improvement. It leverages tester creativity to uncover real-world problems in a way that structured testing cannot.

Question 85: 

Which Agile principle emphasizes collaboration with the customer?

A) Responding to change over following a plan
B) Individuals and interactions over processes and tools
C) Customer collaboration over contract negotiation
D) Working software over comprehensive documentation

Answer: C) Customer collaboration over contract negotiation

Explanation:

Responding to change over following a plan emphasizes flexibility in responding to evolving requirements rather than rigid adherence to pre-defined plans. While related to stakeholder engagement, this principle primarily addresses the team’s adaptability rather than direct collaboration with the customer on a continuous basis.

Individuals and interactions over processes and tools highlights the importance of communication, teamwork, and direct collaboration within the development team. It focuses on internal dynamics, ensuring effective collaboration and decision-making among team members, but does not explicitly prioritize engagement with external stakeholders such as customers.

Working software over comprehensive documentation underscores delivering functional software as the primary measure of progress, rather than exhaustive documentation. This principle values results and tangible output but does not inherently involve working directly with customers to refine requirements or gather feedback.

Customer collaboration over contract negotiation is correct because Agile places a strong emphasis on continuous engagement with customers throughout development. This principle encourages teams to actively involve stakeholders, solicit feedback, and iterate on solutions to meet real needs. By prioritizing collaboration over rigid contract terms, Agile ensures that the delivered product aligns with user expectations, fosters transparency, and strengthens stakeholder satisfaction. This focus on meaningful interaction with customers is central to Agile’s iterative, value-driven approach.

Question 86: 

Which of the following is the purpose of acceptance test-driven development (ATDD)?

A) Define acceptance criteria collaboratively before coding
B) Automate performance tests
C) Replace unit testing
D) Execute exploratory tests only

Answer:  A) Define acceptance criteria collaboratively before coding

Explanation:

Option A, defining acceptance criteria collaboratively before coding, is central to ATDD. In this practice, developers, testers, and stakeholders work together to clarify what “done” looks like for a given feature before any implementation starts. This collaborative approach ensures that everyone shares the same understanding of the desired outcome, which reduces ambiguity and prevents miscommunication that could lead to rework or defects. By establishing clear acceptance criteria early, ATDD promotes alignment with business goals and encourages a shared sense of ownership across the team.

Option B, automating performance tests, is not the main purpose of ATDD. While ATDD can integrate automated tests as part of the workflow, its focus is not specifically on performance. Performance testing deals with system speed, scalability, and stability, which are important but secondary concerns in the ATDD methodology. The primary goal is defining expected functionality and acceptance conditions, not evaluating performance metrics.

Option C, replacing unit testing, is also incorrect. ATDD complements unit testing rather than replacing it. Unit tests check the smallest functional components in isolation, ensuring internal correctness, while ATDD ensures that the overall feature meets the agreed-upon acceptance criteria. Both approaches can coexist: unit tests verify the internal logic, while ATDD verifies that the feature works from a business perspective.

Option D, executing exploratory tests only, is misleading. Exploratory testing is an informal testing approach where testers explore the system to find unexpected issues. While exploratory tests provide valuable insights, ATDD is structured around predefined acceptance criteria and collaborative agreement, which is the opposite of purely exploratory practices.

The reasoning behind selecting Option A is that ATDD emphasizes early alignment, collaboration, and defining success criteria before coding begins. This process reduces misunderstandings, improves the predictability of delivered features, and allows teams to incorporate iterative feedback, ensuring that features meet real business needs. It supports Agile principles by integrating testing and development seamlessly, validating requirements early, and minimizing risk.

Question 87: 

Which Agile ceremony is held to inspect the increment and adapt the backlog based on feedback?

A) Sprint Planning
B) Sprint Review
C) Daily Stand-up
D) Sprint Retrospective

Answer: B) Sprint Review

Explanation:

Option A, Sprint Planning, is a ceremony for selecting backlog items to work on in the upcoming sprint. During planning, the team decides what they can commit to and plans how they will deliver it. While it is essential for setting goals and defining work, it does not focus on inspecting the already completed increment or collecting stakeholder feedback.

Option B, Sprint Review, is designed to demonstrate the completed increment to stakeholders and gather actionable feedback. During this ceremony, the team showcases working software, discusses what has been accomplished, and evaluates whether it meets the agreed-upon acceptance criteria. Stakeholders can then suggest changes or improvements, which are captured and prioritized in the backlog. This iterative feedback loop is central to Agile because it ensures that the product evolves in line with actual user needs rather than assumptions.

Option C, the Daily Stand-up, is a short daily synchronization meeting. It allows team members to communicate progress, plan for the next 24 hours, and address impediments. While it supports coordination, it does not provide an opportunity to inspect completed work with stakeholders or adapt the backlog based on feedback.

Option D, Sprint Retrospective, focuses on improving team processes. During this meeting, the team reflects on what went well, what did not, and identifies actionable improvements. It emphasizes learning and continuous process improvement rather than demonstrating product increments to stakeholders.

The correct answer is Sprint Review because it is the only ceremony specifically designed for inspection of the increment and backlog adaptation. This ensures that development aligns with stakeholder expectations and allows teams to incorporate real-world feedback, fostering continuous improvement and value delivery.

Question 88: 

Which of the following defines the “Definition of Done” in Agile?

A) The criteria that must be met for a backlog item to be considered complete
B) List of all user stories
C) Detailed technical design
D) Sprint goal

Answer:  A) The criteria that must be met for a backlog item to be considered complete

Explanation:

Option A, the criteria that must be met for a backlog item to be considered complete, accurately describes the Definition of Done. This concept establishes a clear, shared understanding among the team of what it means for a feature to be complete and potentially shippable. It ensures consistency, reduces misunderstandings, and improves quality by setting explicit completion standards, including functional requirements, testing, documentation, and compliance considerations.

Option B, the list of all user stories, refers to the product backlog. While the backlog captures what needs to be built, it does not define when a backlog item is complete or meet specific quality standards. The Definition of Done ensures that each item, once marked complete, is fully functional and meets quality expectations.

Option C, a detailed technical design, is a blueprint or plan for implementation. It helps developers understand how to build a feature but does not specify completion criteria or quality standards. Without a Definition of Done, technical designs alone cannot ensure that the work meets the intended business or quality requirements.

Option D, the sprint goal, gives a concise objective for the sprint to guide the team’s work. It provides direction but does not define specific criteria for individual backlog items. The Definition of Done complements the sprint goal by ensuring that each increment delivered within the sprint meets agreed-upon standards.

The correct answer is Option A because the Definition of Done provides a uniform standard for completion that is understood and followed by the entire team. It promotes transparency, consistency, and high quality, ensuring that completed work is functional, tested, and ready for release.

Question 89: 

Which of the following is true about cross-functional Agile teams?

A) Members specialize in one skill only
B) The team possesses all skills needed to deliver a complete increment
C) Team relies on external departments for testing
D) Team focuses only on development

Answer: B) The team possesses all skills needed to deliver a complete increment

Explanation:

Option A, that members specialize in one skill only, contradicts the principle of cross-functionality. Agile teams benefit from having diverse skill sets so that the team can handle all aspects of delivery without being dependent on external resources. Limiting team members to a single specialty reduces flexibility, increases bottlenecks, and slows delivery.

Option B, the team possesses all skills needed to deliver a complete increment, is correct. Cross-functional teams combine analysis, design, development, testing, and deployment capabilities, enabling them to produce potentially shippable increments independently. This setup encourages self-organization, faster iteration, and better collaboration while minimizing dependencies and handoffs.

Option C, relying on external departments for testing, is the opposite of cross-functional behavior. Dependence on other teams creates delays, complicates communication, and introduces risks that Agile seeks to minimize. Agile encourages building teams with all necessary capabilities internally.

Option D, focusing only on development, ignores the need for integrated skills in testing, design, and analysis. A narrow focus prevents teams from delivering fully functional and tested increments, which is essential for Agile’s iterative and incremental approach.

Option B is correct because cross-functional teams are structured to deliver complete increments independently, enabling faster feedback, higher quality, and stronger collaboration.

Question 90: 

Which Agile practice involves integrating code frequently and running automated tests to identify defects early?

A) Continuous Integration
B) Regression Testing
C) Exploratory Testing
D) Load Testing

Answer:  A) Continuous Integration

Explanation:

Option A, Continuous Integration, is the correct practice. It emphasizes frequent merging of code into a shared repository, followed by automated builds and tests. This ensures that integration issues are detected quickly, defects are caught early, and the team maintains a stable codebase. Continuous Integration reduces the risk of late-stage problems and aligns with Agile’s iterative, incremental approach.

Option B, Regression Testing, involves verifying that existing functionality still works after changes. While regression testing is important for quality, it does not involve the frequent code integration and automated build process central to Continuous Integration.

Option C, Exploratory Testing, relies on testers exploring the system to identify unexpected issues. It is primarily a manual and investigative practice, not focused on automated integration or early defect detection through continuous builds.

Option D, Load Testing, evaluates system performance under stress conditions. Although necessary for performance validation, it does not detect integration issues during the development process and is not the main focus of Agile’s defect-prevention practices.

Continuous Integration is the correct answer because it systematically merges code, runs automated tests, and provides immediate feedback, reducing risk, maintaining quality, and supporting Agile principles of early validation and incremental delivery.

Question 91: 

Which Agile artifact is selected and planned for completion within a single sprint?

A) Product Backlog
B) Sprint Backlog
C) Burndown Chart
D) Definition of Done

Answer: B) Sprint Backlog

Explanation:

The Product Backlog is a comprehensive list of all desired features, enhancements, bug fixes, and technical work for the product. It is maintained and prioritized by the Product Owner and acts as a living document that evolves throughout the project. While it contains everything that could eventually be implemented, it is not specific to a single sprint, making it unsuitable as the artifact that defines sprint-specific work. Selecting it alone does not give the team clarity on what must be completed immediately, as it is more of a high-level roadmap.

A Burndown Chart is a visual tool used to track the progress of work over the course of a sprint. It helps teams monitor whether they are on track to complete their planned work, showing the remaining effort against time. While it is valuable for managing and observing progress, it does not itself define what work is planned or included in a sprint. It is purely a tracking and reporting artifact rather than a planning artifact.

The Definition of Done (DoD) establishes the criteria for when a work item or increment is considered complete. It ensures that quality and acceptance standards are consistently applied across the team. However, DoD is a set of conditions rather than a collection of planned work. It helps the team know when a task is finished but does not tell them what tasks are selected for the sprint.

The Sprint Backlog, in contrast, contains the specific user stories, tasks, and backlog items that the team commits to completing in the current sprint. It is derived from the Product Backlog during sprint planning and provides a clear, actionable plan for the team. By including detailed tasks and responsibilities, it allows the team to organize, track, and manage their work efficiently, ensuring they can meet the sprint goal. Because it is explicitly tied to a single sprint and reflects a realistic and achievable plan, it is the correct answer.

Question 92: 

Which of the following best describes a “potentially shippable product increment”?

A) Partially developed code
B) Fully integrated, tested, and ready for release
C) Backlog items not started
D) Test plans only

Answer: B) Fully integrated, tested, and ready for release

Explanation:

Partially developed code represents work in progress. While it may show progress, it cannot be delivered to a user or deployed, and it has not met quality or integration standards. Therefore, it does not meet the definition of a potentially shippable increment, which requires completeness and readiness for deployment.

Backlog items that have not been started are even further from being deliverable. They are ideas or requirements awaiting implementation and do not contribute directly to the product’s usable functionality. Simply having them in a backlog does not provide tangible value to stakeholders or end-users, which is a key principle of Agile delivery.

Test plans alone are important documentation for ensuring quality but are not themselves a product increment. They support the process of creating potentially shippable software by guiding testing, but without implementation, integration, and validation, they cannot be delivered to users.

A potentially shippable product increment is fully integrated, tested, and meets the Definition of Done. It represents a working, functional piece of software that could be released if desired. This ensures that each iteration delivers tangible value, allows for early feedback from stakeholders, and supports incremental progress toward the overall product goals. Because it captures all the necessary qualities of completeness, readiness, and usability, it is the correct choice.

Question 93: 

Which technique is used to generate test cases automatically from business rules or system models?

A) Risk-Based Testing
B) Model-Based Testing
C) Exploratory Testing
D) Ad-hoc Testing

Answer: B) Model-Based Testing

Explanation:

Risk-Based Testing prioritizes testing efforts based on the likelihood and impact of potential failures. While it is valuable for focusing limited testing resources, it does not automatically generate test cases. Its primary goal is to identify the most critical areas to test rather than produce tests from formal models.

Exploratory Testing relies on the tester’s experience, intuition, and creativity to discover defects. It is highly flexible and adaptive but inherently manual and does not use formal models or automated generation. While it uncovers issues that may not be considered in structured testing, it does not produce systematic test cases automatically.

Ad-hoc Testing is informal, often performed without planning or documentation. It is spontaneous and lacks the systematic rigor needed to generate test cases automatically. It is useful for finding unexpected bugs but does not support repeatable, model-based test generation.

Model-Based Testing (MBT) uses system models, workflows, or decision rules to automatically generate test cases. By formalizing system behavior into models, MBT ensures comprehensive coverage, consistency, and repeatability. Tests can be regenerated as the model evolves, increasing efficiency and reducing manual effort. Because it directly creates test cases from models and aligns with automation goals, it is the correct answer.

Question 94: 

Which Agile principle emphasizes delivering working software frequently?

A) Working software over comprehensive documentation
B) Deliver value in short iterations
C) Customer collaboration over contract negotiation
D) Responding to change over following a plan

Answer: B) Deliver value in short iterations

Explanation:

Working software over comprehensive documentation emphasizes that deliverables should prioritize usable software rather than heavy documentation. While this principle underscores the importance of working software, it does not specifically address the frequency of delivery, which is the focus of the question.

Customer collaboration over contract negotiation highlights the value of engaging stakeholders continuously rather than relying solely on formal agreements. It supports iterative delivery indirectly but is primarily about communication and alignment rather than delivery cadence.

Responding to change over following a plan emphasizes flexibility and adaptability in the development process. While it allows teams to adjust delivery priorities, it does not define the principle of frequent incremental delivery explicitly.

Delivering value in short iterations is correct because it requires producing small, usable increments regularly. These increments can be demonstrated to stakeholders, deployed if needed, and provide early feedback for course corrections. This approach embodies the Agile commitment to iterative development and tangible, frequent progress.

Question 95: 

Which statement describes story points?

A) Absolute number of hours for a task
B) Relative measure of effort or complexity
C) Count of defects in a feature
D) Priority assigned by Product Owner

Answer: B) Relative measure of effort or complexity

Explanation:

Story points are not an exact number of hours. Estimating in hours can be misleading because actual effort may vary due to complexity, risk, and unforeseen challenges. Absolute time-based estimates can reduce flexibility and create unrealistic expectations.

Story points are also not the number of defects in a feature. Counting defects measures quality or testing results, not the effort required to implement a story. Using defects as a proxy for effort would misalign planning and velocity calculations.

Story points are not priority indicators either. Prioritization is typically determined by the Product Owner based on business value, risk, and strategic considerations. While priority guides what the team works on, it is separate from estimating effort or complexity.

Story points are a relative measure that combines complexity, risk, and effort to allow teams to estimate work consistently. Teams compare stories to each other rather than assigning absolute values, enabling them to plan sprints effectively, calculate velocity, and adapt their commitments as experience grows. This relative sizing makes option B the correct answer.

Question 96: 

Which ceremony is primarily for the team to synchronize and plan daily work?

A) Sprint Planning
B) Daily Stand-up
C) Sprint Review
D) Sprint Retrospective

Answer: B) Daily Stand-up

Explanation:

Sprint Planning is a ceremony that occurs at the start of a sprint, where the team discusses the work that needs to be completed during the upcoming sprint. Its primary focus is on defining the sprint backlog and setting sprint goals, ensuring alignment with the product backlog and overall project objectives. While Sprint Planning involves collaboration and planning, it does not facilitate daily synchronization of ongoing work, making it unsuitable for the purpose described in this question.

Sprint Review is conducted at the end of the sprint to inspect the increment and gather feedback from stakeholders. It focuses on reviewing what was completed, demonstrating new features, and adjusting the product backlog based on stakeholder input. Although Sprint Review provides valuable insight and supports adaptation, it is not designed to support the team’s daily work coordination.

Sprint Retrospective, on the other hand, is focused on continuous improvement. The team reflects on its processes, identifies strengths and weaknesses, and creates actionable steps for improvement in the next sprint. While Retrospective fosters long-term team effectiveness, it does not address day-to-day task coordination, progress tracking, or obstacle removal.

Daily Stand-up is the correct answer because it is a short, time-boxed meeting where team members share what they worked on yesterday, what they plan to work on today, and any impediments they are facing. This ceremony ensures transparency, enables rapid problem-solving, and maintains team alignment on a daily basis. By providing a forum for communication and coordination, the Daily Stand-up supports Agile principles of collaboration, adaptability, and fast feedback loops.

Question 97: 

Which of the following is true about regression testing in Agile?

A) Performed only at project end
B) Ensures previously working functionality remains intact after changes
C) Replaces exploratory testing
D) Focuses solely on performance

Answer: B) Ensures previously working functionality remains intact after changes

Explanation:

Option A is incorrect because regression testing in Agile is not limited to the end of the project. Agile promotes iterative and incremental delivery, which means code is continuously updated and deployed. Performing regression tests only at the end would risk introducing defects in earlier iterations and would go against the principles of frequent feedback and continuous quality assurance.

Option C is also incorrect because regression testing does not replace exploratory testing. Exploratory testing emphasizes learning, adaptability, and uncovering unknown defects, whereas regression testing is systematic and ensures that existing functionality continues to work correctly after changes. Both testing approaches are complementary in Agile, each serving a different purpose in maintaining software quality.

Option D is misleading because regression testing does not focus solely on performance. While performance testing can be part of a regression suite, regression testing primarily verifies the correctness of previously implemented functionality, ensuring that new changes do not unintentionally break existing features. Performance, security, and usability testing are separate considerations.

Option B is correct because regression testing in Agile ensures that functionality which previously worked continues to function as expected after code changes, updates, or refactoring. By catching unintended side effects early, regression testing supports Agile’s iterative development model, allowing teams to maintain software stability and reduce technical debt while continuously delivering value.

Question 98: 

Which Agile practice encourages testers to be involved early and throughout the development lifecycle?

A) Shift-left testing
B) Load testing
C) Smoke testing
D) Ad-hoc testing

Answer:  A) Shift-left testing

Explanation:

Option B, load testing, is concerned with evaluating the system’s behavior under high load conditions, usually performed after major features are implemented or in pre-release stages. It does not inherently promote early or continuous involvement of testers throughout the development lifecycle, so it does not align with the principle described in the question.

Option C, smoke testing, is a quick verification to ensure that the basic functionalities of the system are working after a build. While useful for validating major functionality, smoke testing typically occurs after development milestones rather than as an ongoing, early-stage collaborative activity.

Option D, ad-hoc testing, is informal and unstructured, often performed spontaneously by testers without predefined scripts. While it can uncover unexpected issues, it is reactive rather than proactive and does not formalize early involvement in planning, design, or development discussions.

Shift-left testing is the correct choice because it emphasizes integrating testing activities early in the development lifecycle, sometimes even during requirements and design phases. By involving testers from the start, teams can identify potential defects sooner, improve collaboration between development and quality assurance, and provide continuous feedback. This approach aligns with Agile values of iterative development, early validation, and maintaining high software quality throughout the project.

Question 99: 

Which Agile ceremony focuses on process improvement and identifying actionable steps?

A) Sprint Planning
B) Sprint Review
C) Sprint Retrospective
D) Daily Stand-up

Answer: C) Sprint Retrospective

Explanation:

Option A, Sprint Planning, is primarily focused on preparing for the upcoming sprint by defining the sprint backlog and selecting the work items that the team will complete during the iteration. This ceremony involves the team and the product owner discussing the priorities from the product backlog, estimating effort, and setting a clear sprint goal. While Sprint Planning is essential for providing direction and clarity about what the team intends to accomplish, it is focused on planning and scope definition rather than on evaluating team performance or processes. It establishes a roadmap for the sprint but does not create an opportunity for the team to reflect on how they worked together or to identify actionable improvements for future sprints. Therefore, while valuable for guiding work, it does not meet the requirement of focusing on process improvement.

Option B, Sprint Review, occurs at the end of the sprint and is aimed at inspecting the completed increment of the product. During this ceremony, the team demonstrates the features they have implemented to stakeholders, collects feedback, and discusses any necessary adjustments to the product backlog. The primary goal of the Sprint Review is product-centric: it assesses the delivered functionality, evaluates whether it meets stakeholder expectations, and identifies what should be prioritized next. While it provides valuable insights into product development, it does not focus on the team’s internal processes, collaboration methods, or ways to improve how the team works together. Its scope is on the outcome of the work, rather than the methods used to achieve it.

Option D, Daily Stand-up, is a brief, time-boxed meeting where team members share updates on what they accomplished yesterday, what they plan to work on today, and any obstacles they face. This ceremony is essential for daily coordination, maintaining transparency, and quickly addressing immediate issues. While it can highlight short-term process problems or bottlenecks, it is not structured to allow the team to perform deeper reflection on processes, identify systemic improvements, or develop actionable plans for process enhancement over the long term. Its focus is operational and immediate rather than strategic and reflective.

Sprint Retrospective is the correct answer because it is specifically designed for evaluating and improving the team’s processes. During the Retrospective, the team reflects on the past sprint to discuss what went well, what did not go as expected, and what changes could improve effectiveness, collaboration, and overall performance. Actionable steps are identified to implement improvements in the next sprint, fostering a culture of continuous learning and adaptation. By concentrating on process evaluation and actionable change, the Retrospective ensures that the team evolves and improves iteratively, aligning perfectly with Agile principles of continuous improvement and self-organizing teams.

Question 100: 

Which of the following describes exploratory testing?

A) Scripted and repeatable
B) Unscripted, adaptive, and based on tester knowledge
C) Performance-focused only
D) Automates all test cases

Answer: B) Unscripted, adaptive, and based on tester knowledge

Explanation:

Option A is incorrect because scripted testing relies on predefined test cases that are executed in a structured, repeatable manner. Each test is planned in advance, with detailed steps and expected results, leaving little room for creativity or adaptation during execution. Exploratory testing, in contrast, is intentionally flexible and adaptive. It empowers testers to use their skills, intuition, and domain knowledge to investigate the software in real time, responding dynamically to behaviors and anomalies they encounter. Unlike scripted tests, exploratory testing does not follow rigid instructions, allowing testers to explore different paths, experiment with inputs, and uncover issues that might not be anticipated during initial planning.

Option C is also inaccurate because exploratory testing is not focused solely on performance. While performance can be one aspect evaluated during testing, the primary goal of exploratory testing is broader: to discover defects through active investigation, learning, and experimentation. Limiting exploratory testing to performance would ignore its core purpose of uncovering unexpected issues, understanding system behavior under various conditions, and continuously adapting the testing approach based on new insights. It is designed to be responsive to changes in requirements and software behavior, which makes it particularly valuable in Agile environments where the system evolves rapidly.

Option D is misleading because exploratory testing is not about automating test cases. Automation scripts are predefined, execute consistently, and are limited to the scenarios that have been explicitly programmed. Exploratory testing, on the other hand, is human-centered. It leverages the tester’s cognitive abilities to observe, analyze, and respond to the system in ways that automated tests cannot. While automation can complement exploratory testing by handling repetitive checks, it cannot replace the adaptive, investigative, and creative process that defines exploratory testing. The tester’s judgment and real-time decision-making are central to its effectiveness.

Option B is correct because exploratory testing is unscripted, adaptive, and relies heavily on the tester’s knowledge, experience, and intuition. Testers dynamically explore the software, make decisions based on observations, and adapt their approach as new information emerges. This method allows teams to uncover defects that are difficult to predict and evaluate scenarios that scripted or automated tests might miss. In Agile environments, where requirements frequently change and delivery cycles are short, exploratory testing provides timely insights into software quality, helping teams respond quickly to risks and maintain a high level of product reliability. It encourages continuous learning and aligns with Agile principles of adaptability, collaboration, and iterative improvement.