Up To Date Certified Tester Foundation Level Agile Tester CTFL-AT Exam Question

NEW QUESTION 1
Which of the following sentences about the integration of development and testing activities
in Agile projects is INCORRECT?

• A. While developers develop automated unit test scripts, testers write automated system level tests.
• B. Testers replace developers in writing unit test automation scripts.
• C. Developers write acceptance criteria and test cases, together with testers.
• D. Developers and testers may work as a pair to develop and test a feature.

Answer: B

Explanation:
Testers replace developers in writing unit test automation scripts. Comprehensive Explanation: The integration of development and testing activities in Agile projects is based on the principle of cross-functional teamwork, where all team members collaborate and share their skills and knowledge to achieve a common goal. In the context of testing, this means that testing is not seen as a separate activity or phase, but as an integral part of the development process. Therefore, the following sentences are correct:
✑ While developers develop automated unit test scripts, testers write automated system level tests. This is an example of how developers and testers can work in parallel and complement each other’s testing efforts. Developers can focus on testing the internal quality of the code, while testers can focus on testing the external quality of the product.
✑ Developers write acceptance criteria and test cases, together with testers. This is an example of how developers and testers can work together to define and verify the user requirements and expectations. Developers can provide their technical expertise and input, while testers can provide their business and user perspective and feedback.
✑ Developers and testers may work as a pair to develop and test a feature. This is an example of how developers and testers can work closely and interactively to deliver a feature. Developers and testers can exchange ideas, suggestions, and information, and support each other in the coding and testing tasks.
The following sentence is incorrect:
✑ Testers replace developers in writing unit test automation scripts. This is not a valid example of the integration of development and testing activities in Agile projects, because it implies that testers take over the responsibility of developers, rather than collaborate with them. Testers should not replace developers in writing unit test automation scripts, because developers have more knowledge and experience in coding and debugging, and because unit testing is an essential part of the development process. Testers should instead work with developers to ensure that the unit test automation scripts are adequate, effective, and maintainable. References: ISTQB® Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB® Glossary of Testing Terms2, version 4.0, pages 16 and 55.

NEW QUESTION 2
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 3
Which of the following is a benefit of a whole-team approach?

• A. Enables reduction in test duplication as the testers and test engineers function as a single team.
• B. Enables testers to execute their responsibility for quality for the combined team.
• C. Enables the team to focus on solely their separate areas of expertise and responsibility.
• D. Enables the various skill sets within the team to be leveraged to the benefit of the project.

Answer: D

Explanation:
A whole-team approach is a way of working in agile projects where all team members share the responsibility for delivering high-quality software that meets the customer’s needs. This means that testers, developers, business analysts, and other roles collaborate closely throughout the project lifecycle, and use their different skills and perspectives to contribute to the quality of the product. A benefit of this approach is that it enables the team to leverage the various skill sets within the team to the benefit of the project, such as testing skills, coding skills, domain knowledge, user experience, etc. This can lead to faster feedback, better communication, higher productivity, and more innovation. References: ISTQB® Foundation Level Agile Tester Syllabus1, Section 1.1.1, page 7; ASTQB Agile Tester Certification Resources, Section 1.1.1, page 7.

NEW QUESTION 4
Which of the following statements about the Planning poker test estimate technique are CORRECT?
1) Planning poker is a consensus based technique using a deck of cards.
2) A low test estimate usually means the story should be broken down into multiple smaller stories.
3) A high test estimate usually means the story should be broken down into multiple smaller stories.
4) One poker round is played and then consensus has to be reached.
5) The risk level of each backlog item should be decided before the poker session.

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

Answer: A

Explanation:
Planning poker is a consensus-based technique for agile estimation, using a deck of cards with predefined numerical values, usually based on the Fibonacci sequence or a modified version12. Therefore, statement 1 is correct. A high test estimate usually means that the user story or task is too complex, ambiguous, or risky, and should be broken down into multiple smaller stories that are easier to understand and estimate13. Therefore, statement 3 is correct. The risk level of each backlog item should be decided before the poker session, as it can affect the estimation process and the prioritization of the work14. Therefore, statement 5 is correct. Statement 2 is incorrect, as a low test estimate usually means that the user story or task is simple, clear, and well-defined, and does not need to be broken down further13. Statement 4 is incorrect, as planning poker can involve multiple rounds of estimation, reveal, and discussion, until the team reaches a consensus or agrees to defer the item12. References: 1: ISTQB® Foundation Level Agile Tester Syllabus, Section 3.3.1, Test Automation1; 2: ASTQB Agile Tester Certification Resources, Section 3.3.1, Test Automation2; 3: Planning Poker: An Agile Estimating and Planning Technique3; 4: Planning poker: The all-in strategy for Agile estimation - Asana4

NEW QUESTION 5
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 6
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 7
You are a tester in an agile team. The user story you are due to test is still under development so your tests are blocked. The main issue holding progress on this user story is that the developer's unit tests are constantly failing.
As an agile tester, which of the following actions should you take?

• A. Review the design of the problematic user story and improve it where possible.
• B. Create a bug report for each of your blocked tests.
• C. Work together with the developer, suggesting reasons why the tests are failing.
• D. Use the time to improve and automate existing test cases of other user stories.

Answer: C

Explanation:
As an agile tester, you should work together with the developer, suggesting reasons why the tests are failing. This is an example of the agile principle of collaboration and communication within the team, as well as the agile testing practice of early and frequent feedback. By working together with the developer, you can help to identify and resolve the root causes of the test failures, as well as share your testing knowledge and perspective. This can lead to faster and better quality delivery of the user story, as well as improved team relationships and trust.
Option A is not a good action, because reviewing and improving the design of the user story is not the tester’s responsibility, and it may not address the test failures. Option B is also not a good action, because creating bug reports for blocked tests is not an agile way of handling issues, and it may create unnecessary overhead and waste. Option D is not a good action, because it does not help to unblock the current user story, and it may distract you from the sprint goal and the team’s focus.
References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.1, page 171; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.1-2, page 82

NEW QUESTION 8
Consider an online application that allows registered users to pay the annual car tax based on the vehicle’s engine power in kW. Given the following user story:
"As a customer I need the online application to calculate the annual car tax amount that I need to pay for my car:
* If the power of the vehicle is less than 20 kW, then the annual car tax is free
* If the power of the vehicle is more or equal than 20 kW but less or equal than 150 kW, then the annual car tax is 250 Euros
* If the power of the vehicle is more than 150 kW, then the annual car tax is 750 Euros" What is the MOST suitable use of a black-box test design technique for this user story?

• A. Decision table testin
• B. Test the following conditions:Conditions=registered user logged in; inserted power of the vehicle=20kW; Action=Car tax paid
• C. State transition testin
• D. Test the transitions between the following states: logging in, inserting the power of the vehicle, making payment, logging ou
• E. Equivalence partitionin
• F. Test the annual car tax value for the following partitions: [power of the vehicle<20 kW ; 20 kW power of the vehicles150 kW; power of the vehicle>150 kW]
• G. Use case testing Test the following use case (Actor=registered user): Pre-condition=registered user logged in Scenario=registered user inserts the power of the vehicle, making payment and logs out Post-condition=car tax paid and registered user logged out

Answer: C

Explanation:
Equivalence partitioning is a black-box test design technique that divides the input domain of a system into classes of data from which test cases can be derived. The idea is that if a system works correctly for a representative value from an equivalence class, it will work correctly for all values from that class, and vice versa. Equivalence partitioning reduces the number of test cases by eliminating redundant ones. For the given user story, equivalence partitioning is the most suitable technique because it can test the different outcomes of the annual car tax calculation based on the power of the vehicle, which is the main input for the system. By testing one value from each partition, the tester can verify the functionality of the system and detect any errors in the calculation logic. The other techniques are not as suitable because they do not focus on the inputdomain of the system, but rather on the conditions, transitions, or scenarios that are not directly related to the user story. References:
✑ : ISTQB® Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2
✑ : ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2
✑ : 3

NEW QUESTION 9
What is the main benefit of the Test Pyramid?

• A. It means testing is involved early in the development cycle.
• B. It helps in evaluating the amount of test cases needed.
• C. It shows complexity of testing activities.
• D. It acts as a metric for testing progress.

Answer: B

Explanation:
The Test Pyramid is a model for organizing tests in a way to make the process of testing faster, efficient and cost-effective. This model focusses on getting maximum functional testing getting covered by faster and less brittle tests like Unit and API tests1. The main benefit of the Test Pyramid is that it helps in evaluating the amount of test cases needed for each level of testing. The Test Pyramid suggests that the number of test cases should decrease as we move up the pyramid, from unit tests to integration tests to end-to-end tests. This is because unit tests are more granular, isolated, and easy to write and maintain, while end-to-end tests are more complex, dependent, and brittle. The Test Pyramid also helps in balancing the test coverage and the test execution time, as unit tests provide high coverage and low execution time, while end-to-end tests provide low coverage and high execution time. By following the Test Pyramid, teams can optimize their testing efforts and resources, and ensure that they have a sufficient and effective test suite for their software. References: ISTQB® Foundation Level Agile Tester Syllabus, Section 2.2.1, page 16; ASTQB Agile Tester Certification Resources, Section 2.2.1, page 16; What is Test Pyramid : Getting started with Test Automation Pyramid, The Practical Test Pyramid - Martin Fowler, Testing Pyramid: What Is It and How To Use It | Solvd.

NEW QUESTION 10
Which ONE of the following is an example of a typical “Business-oriented work product”?

• A. The released product.
• B. Acceptance testing entry criteria.
• C. A user manual.
• D. Usability testing test results.

Answer: C

Explanation:
Business-oriented work products are those that describe what is needed (e.g., requirements specifications) and how to use it (e.g., user documentation). A user manual is an example of a business-oriented work product, as it provides instructions and guidance on how to use the product from the user’s perspective. A user manual may also contain information about the product’s features, benefits, and limitations. A user manual is typically written by technical writers, who may collaborate with developers, testers, and business analysts to ensure the accuracy and clarity of the content. A user manual may be delivered in various formats, such as printed, online, or interactive. References: ISTQB® Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 10; ASTQB Agile Tester Certification Resources2, Section 1.2.1, page 10.

NEW QUESTION 11
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 12
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 13
......