CTFL-AT Exam - Certified Tester Foundation Level Agile Tester

NEW QUESTION 1
During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?

• A. The build process was slow and this often caused delays waiting for the build to complete.
• B. For the last sprint the estimated and actual effort were much higher than the team capacity.
• C. The automation tests failed frequently without any logs to help in debugging the failure reason.
• D. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.

Answer: D

Explanation:
According to the ISTQB Tester Foundation Level Agile Tester syllabus, a retrospective is a meeting held at the end of each iteration or release, where the agile team reflects on what went well and what can be improved in their processes, practices, and interactions. The purpose of a retrospective is to identify and implement actions for continuous improvement, and to foster a culture of learning and collaboration. Therefore, the items that would be the most effective to generate discussions on process improvement are those that are related to the team’s performance, challenges, feedback, and suggestions. Option D is the least effective item to generate discussions on process improvement, as it is a personal attack on one of the team members, and it does not offer any constructive feedback or solution. This kind of item can create a negative and hostile atmosphere in the retrospective, and damage the trust and respect among the team members. Option A is an effective item to generate discussions on processimprovement, as it identifies a problem with the build process that affects the team’s efficiency and quality, and it can lead to finding ways to optimize the build process or to mitigate the delays. Option B is also an effective item to generate discussions on process improvement, as it reveals a discrepancy between the team’s estimation and actual effort, and it can lead to analyzing the root causes of the deviation and to improving the estimation techniques or the team’s capacity. Option C is also an effective item to generate discussions on process improvement, as it highlights a weakness in the automation tests that hinders the team’s ability to debug and fix the failures, and it can lead to enhancing the automation tests with
better logging mechanisms or to reviewing the automation strategy. References: ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.1, page 14; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.2, page 15; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.1, page 16; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.2, page 17.

NEW QUESTION 2
Why is regression of software a high risk in agile projects?

• A. Test-driven development means that existing functionality is not considered.
• B. Test automation can cause regression of software in the test environment.
• C. Regression is built into software as a safeguard against unexpected failures.
• D. There is code churn due to change in business needs over several sprints.

Answer: D

Explanation:
Regression of software is the risk that a change in one part of the software causes a defect in another part of the software that was previously working correctly. Regression of software is a high risk in agile projects because there is code churn due to change in business needs over several sprints. Code churn is the amount of code that is added, modified, or deleted in a software project over time. Code churn can indicate the volatility and complexity of the software, and the frequency and magnitude of the changes. In agile projects, code churn can be high because the business needs and the user requirements can change rapidly and frequently over several sprints, which are short iterations of development and testing. This means that the software is constantly evolving and adapting to the changing needs, and that the existing functionality and quality may be affected by the new or modified code. Therefore, regression of software is a high risk in agile projects, and it requires effective testing strategies and techniques to prevent, detect, and fix the regression defects. References: ISTQB® Foundation Level Agile Tester Syllabus1, Section 2.3.2, page 17; ISTQB® Glossary of Testing Terms2, version 4.0, pages 36 and 55

NEW QUESTION 3
Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan.
In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?

• A. Exploratory Testing
• B. Prototype Testing
• C. Performance Testing
• D. Functional Testing

Answer: A

Explanation:
Exploratory testing is a type of testing that involves simultaneous learning, test design, and test execution. It is suitable for Quadrant 3 because it is business facing
and product critique, meaning that it focuses on the user’s perspective and the quality attributes of the product. Exploratory testing can help discover new risks, requirements, and defects that may not be covered by other test levels and test types. It can also provide feedback on the usability, functionality, and reliability of the product. References: ISTQB® Foundation Level Agile Tester Syllabus1, Section 2.3.2, page 17; ISTQB® Glossary of Testing Terms2, version 4.0, page 23.

NEW QUESTION 4
Which of the following activities are done in release planning?
1) Identifying testable user stories with acceptance criteria.
2) Elaborating the user stories into tasks.
3) Prioritizing the user stories.
4) Creating acceptance tests for the user stories.
5) Analyzing risks for each of the user stories.
6) Performing high level estimation for the release.

• A. Activities 1, 4 and 6
• B. Activities 2 and 4
• C. Activities 2, 3 and 5
• D. Activities 1, 3 and 6

Answer: D

Explanation:
Release planning is a process of defining the scope and timeline for an iterative or incremental product development project. It is used in agile or hybrid projects where a mid- to long-term planning of the product or system development or integration is required12. Release planning involves the following activities:
✑ Identifying testable user stories with acceptance criteria. User stories are short descriptions of the features or functionalities that the customer or user wants from the product. Acceptance criteria are the conditions that must be met for the user story to be considered done and acceptable. Identifying testable user stories with acceptance criteria helps to define the scope and quality of the release13.
✑ Prioritizing the user stories. User stories are prioritized based on the value they deliver to the customer or user, as well as the dependencies, risks, and costs associated with them. Prioritizing the user stories helps to determine the order and frequency of the releases13.
✑ Performing high level estimation for the release. High level estimation is a technique to estimate the effort, time, and resources needed to complete the user stories in the release. High level estimation can be done using various methods, such as analogy, expert judgment, planning poker, etc. Performing high level estimation for the release helps to set realistic and achievable goals and deadlines13.
Therefore, activities 1, 3 and 6 are done in release planning. Activities 2, 4 and 5 are done in iteration planning, which is a more detailed and short-term planning of the work to be done in each iteration or sprint13. References: 1: ISTQB® Foundation Level Agile Tester Syllabus, Section 2.2, Fundamental Agile Testing Principles, Practices and Processes1; 2: Agile Release Planning in Hybrid and Agile Projects4; 3: How to Create an Agile Release Plan5

NEW QUESTION 5
User Story: As a user I want to be able to calculate tax percentage based on amount of income.
What is the best black box test design technique for verifying the accuracy of this user story?

• A. Statement testing - test all statements in income calculation.
• B. User story testing - test that the user can enter an income amount and get a result.
• C. State transition testing - test all states of income entry.
• D. Equivalence partitioning - test with low, medium and high income.

Answer: D

Explanation:
The best black box test design technique for verifying the accuracy of this user story is equivalence partitioning. Equivalence partitioning is a technique that divides the input domain of a system into classes or groups that are expected to behave similarly. By testing one value from each class, the tester can reduce the number of test cases while still achieving good coverage. In this case, the input domainof the system is the amount of income, which can be divided into classes based on the tax percentage applied to different income ranges. For example, if the tax percentage is 10% for income below 10,000, 20% for income between 10,000 and 20,000, and 30% for income above 20,000, then the equivalence classes are: low income (<10,000), medium income (10,000-20,000), and high income (>20,000). By testing one value from each class, such as 5,000, 15,000, and 25,000, the tester can verify that the system calculates the correct tax percentage for each income range. This technique is more efficient and effective than testing all possible values of income, or testing only one value of income, or testing the states of income entry, or testing the statements in income calculation. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.1, page 19; ISTQB Foundation Level Agile Tester Extension Sample Exam Questions2, Question 5, page 6.

NEW QUESTION 6
Which of the following statements about Agile retrospectives is CORRECT?

• A. During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities.
• B. In an Agile retrospective the moderator can encourage and make sure that good practices are kept by the team, by asking what the team is doing well.
• C. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.
• D. Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.

Answer: B

Explanation:
An Agile retrospective is a regular meeting where the team reflects on their work process and identifies the areas for improvement12. The following statements about Agile retrospectives are correct12:
✑ During Agile retrospectives, testers should be encouraged to provide constructive
suggestions on both testing and non-testing activities, as testing is an integral part of the Agile team and testers can contribute to the overall quality of the product and the process.
✑ In an Agile retrospective, the moderator can encourage and make sure that good practices are kept by the team, by asking what the team is doing well. This helps to reinforce the positive aspects of the team’s work and to appreciate the team members’ efforts and achievements.
✑ Agile retrospectives should be focused mainly on impediments that are within the control of the team because these issues are more actionable and can be resolved by the team. Impediments that are outside the control of the team should also be discussed, but they may require the involvement of other stakeholders or external parties to be addressed.
The following statement about Agile retrospectives is incorrect12:
✑ Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do require follow-up activities. The team should agree on the action items that result from the retrospective and assign them to the responsible team members. The team should also monitor the progress and effectiveness of the action items in the next iteration and review them in the next retrospective.
Therefore, the correct answer is B, as it is the only statement that is correct about Agile retrospectives. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 24; ISTQB Agile Tester Sample Exam2,

NEW QUESTION 7
Which one of the following is a testable acceptance criterion?

• A. The solution shall support business processes.
• B. The system shall be easy to use.
• C. The response time to confirm a customer submission must not exceed 5 seconds.
• D. The tools for testing are tested before use and are meeting the requirements.

Answer: C

Explanation:
A testable acceptance criterion is a condition that can be verified or measured objectively by the tester, customer, or stakeholder. It should be specific, measurable, achievable, relevant, and time-bound (SMART). A testable acceptance criterion should also be written from the user’s perspective, achievable within the sprint, and written before development begins1.
Among the four options, only option C meets these criteria. It is specific (the response time to confirm a customer submission), measurable (must not exceed 5 seconds), achievable (within the technical and business constraints), relevant (to the user’s needs and expectations), and time-bound (must be met in every sprint). It is also written from the user’s perspective, testable (by measuring the response time), and written before development (as part of the user story definition).
Option A is not testable because it is vague and subjective. What does it mean to support business processes? How can this be verified or measured? Option B is also not testable because it is subjective and ambiguous. What does it mean to be easy to use? How can this be verified or measured? Option D is not testable because it is not written from the user’s perspective. It is an internal quality criterion for the testing team, not an acceptance criterion for the product or feature.
References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 182; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.2-2, page 93

NEW QUESTION 8
You have been asked to execute an exploratory testing session on Park & Ride system. The test charter has been titled as “Buy a bus ticket”. As a result, a number of defects were
reported, the titles of which are listed below.
Which defect is out of scope for the given test charter?

• A. Price for a bus ticket was calculated incorrectly.
• B. Failed to buy a bus ticket after 18:00.
• C. Failed to buy a bus ticket when the network connection to the Central System is down.
• D. Payment for parking ticket is restricted to cash only (no credit card supported).

Answer: D

Explanation:
The test charter for the exploratory testing session is focused on buying a bus ticket, not a parking ticket. Therefore, any defect related to the payment for parking ticket is out of scope for the given test charter. The other defects are related to the functionality, usability, or reliability of buying a bus ticket, which are in scope for the test charter. References: ISTQB Certified Tester Foundation Level Agile Tester Extension Syllabus, Version 2014, Section 2.3.2 Exploratory Testing1, Section 2.3.2.1 Test Charter2; ISTQB Glossary of Testing Terms, Version 3.2, 2017, Definition of Test Charter3 1: ISTQB Certified Tester Foundation Level Agile Tester Extension Syllabus, Version 2014, Section 2.3.2 Exploratory Testing 2: ISTQB Certified Tester Foundation Level Agile Tester Extension Syllabus, Version 2014, Section 2.3.2.1 Test Charter 3: [ISTQB Glossary of Testing Terms, Version 3.2, 2017, Definition of Test Charter]

NEW QUESTION 9
Which tasks are typically performed by a tester on an Agile project?
1) Implementing test strategy.
2) Documenting business requirements.
3) Measuring and reporting test coverage.
4) Coaching development team in relevant aspects of testing.
5) Executing test-driven development tests.

• A. 2, 5
• B. 2, 4, 5
• C. 1, 3, 4
• D. 1, 3

Answer: C

Explanation:
A tester on an Agile project typically performs the following tasks12:
✑ Implementing test strategy: A tester helps to define and implement the test strategy for the Agile project, which includes the test approach, test levels, test types, test techniques, test tools, test environment, test data, test metrics, and test documentation.
✑ Measuring and reporting test coverage: A tester measures and reports the test coverage of the product features and quality attributes, such as functionality, usability, performance, security, etc. Test coverage can be expressed in terms of test cases, test scenarios, test sessions, test conditions, test data, code, etc.
✑ Coaching development team in relevant aspects of testing: A tester coaches the development team in relevant aspects of testing, such as test design, test execution, test automation, test-driven development, behavior-driven development, exploratory testing, etc. A tester also helps the development team to improve their testing skills and practices.
The following tasks are not typically performed by a tester on an Agile project:
✑ Documenting business requirements: Business requirements are usually documented by the product owner or the business analyst, not by the tester. The tester may review and provide feedback on the business requirements, but the tester is not responsible for documenting them.
✑ Executing test-driven development tests: Test-driven development tests are usually executed by the developers, not by the tester. The tester may assist the developers in creating and reviewing the test-driven development tests, but the tester is not responsible for executing them.
Therefore, the correct answer is C, as it contains the tasks that are typically performed by a tester on an Agile project. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, pages 14-15, 18-19, 22-23; ISTQB Agile Tester Sample Exam2, question 17.

NEW QUESTION 10
Which of the following describes the main purpose of a task management tool in agile projects?

• A. A task management tool is used by team members to share ideas and collaborate on assigned tasks.
• B. A task management tool is used to manage and track user stories, tests and other tasks.
• C. A task management tool is used to store source code and automated tests.
• D. A task management tool allows developers to continuously integrate their code.

Answer: B

Explanation:
A task management tool is a software application that helps agile teams plan, organize, and monitor their work. A task management tool typically allows the team to create, assign, prioritize, update, and track user stories, tests, and other tasks that are part of the agile project. A task management tool can also provide various views and reports to visualize the progress and status of the project, such as Kanban boards, burndown charts, velocity charts, etc. Some examples of task management tools are Jira, Trello, Asana, and Monday.com12345. References: ISTQB® Foundation Level Agile Tester Syllabus, Section 2.1.1, page 13; ASTQB Agile Tester Certification Resources, Section 2.1.1, page 13.

NEW QUESTION 11
Which of the following is a risk that continuous integration introduces?

• A. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
• B. Testers sometimes have too many builds to test, which reduces the quality of testing.
• C. Teams no longer have the ability to run manual tests, as all tests must be automated.
• D. Developer's workload is increased, which can result in a reduction of output.

Answer: B

Explanation:
Continuous integration is a practice of integrating code changes frequently and automatically into a shared repository, and running automated tests to verify the integration. Continuous integration can introduce some risks to the testing process, such as:
✑ Testers sometimes have too many builds to test, which reduces the quality of testing. This can happen when the code changes are too frequent or too large, and the testers do not have enough time or resources to test each build thoroughly. This can lead to missed defects, incomplete test coverage, and reduced confidence in the product quality.
✑ Testers sometimes have to deal with unstable or broken builds, which affects the testability of the product. This can happen when the code changes introduce errors or conflicts that cause the build to fail or malfunction. This can waste the testers’ time and effort, and delay the feedback cycle.
✑ Testers sometimes have to cope with changing requirements and priorities, which affects the test planning and execution. This can happen when the stakeholders or customers provide new or modified requirements or feedback during the development cycle. This can require the testers to adapt their test strategy, test cases, and test data accordingly, and to balance the testing of new features and regression testing of existing features. References: ISTQB® Foundation Level Agile Tester Syllabus1, Section 2.2.3, page 14; ISTQB® Glossary of Testing Terms2, version 4.0, page 15.

NEW QUESTION 12
Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?

• A. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
• B. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
• C. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
• D. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.

Answer: D

Explanation:
The Agile processes promote early and frequent feedback from the customers, users, testers, developers, and other stakeholders involved in the project. This feedback helps to ensure that the product meets the expectations and needs of the customers and users, and that the development process is continuously improved and adapted to the changing requirements and environment. However, increasing the frequency of feedback and communication does not eliminate all communication problems, as there may still be issues such as misunderstandings, misinterpretations, conflicts, or cultural differences that need to be resolved. Therefore, the statement D is not true, as it implies that communication problems are completely avoided by the Agile processes. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Foundation Level Agile Tester Extension Sample Exam Questions2, Question 4, page 5.

NEW QUESTION 13
......