Enhance Your Career With Available Preparation Guide for CTFL-AT Exam
Get Special Discount Offer of CTFL-AT Certification Exam Sample Questions and Answers
The ISQI CTFL-AT exam covers various topics related to agile testing, including agile software development, testing in agile projects, testing methods and techniques, agile testing processes, and tools used in agile testing. CTFL-AT exam is designed to test the candidate's understanding of agile testing concepts and their ability to apply them in real-world scenarios. Candidates who pass the CTFL-AT exam will be able to demonstrate their in-depth knowledge of agile testing practices and their ability to work effectively in agile teams, making them valuable assets to any software development team.
To prepare for the CTFL-AT certification exam, candidates can attend training courses offered by accredited training providers. These courses cover all the topics included in the exam and provide hands-on experience in agile testing. Candidates can also opt for self-study options, including reading books, watching videos, and taking practice tests. It is recommended that candidates have at least six months of experience working in an agile environment before attempting the exam.
NEW QUESTION # 29
You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.
The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.
A User Story for the Operator-Instructions module is as follows:
"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."
The following is a list of risks identified for this story, with assigned probability and impact.
- A. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
- B. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- C. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low - D. A small child may try to steam milk. Probability: High. Impact: Low
Answer: B
Explanation:
Explanation
Risk-based testing is a technique that prioritizes testing activities based on the level of risk associated with each feature or requirement. The level of risk is usually calculated by multiplying the probability and impact of each risk. The higher the risk level, the more testing effort should be allocated to mitigate the risk. In this case, the risk level for each option is as follows:
A). Risk level = Low x Low = Low
B). Risk level = Low x High = Medium
C). Risk level = High x High = High
D). Risk level = High x Low = Medium
Therefore, the highest risk level is C, followed by B and D, and then A.
The User Story for the Operator-Instructions module should be tested according to this risk order, starting with C, then B, then D, and finally A.
Hence, the answer is B, as it is the second highest risk level and should be tested after C.
References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 16; ISTQB Agile Tester Sample Exam2, question 18.
NEW QUESTION # 30
You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.
The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.
A User Story for the Operator-Instructions module is as follows:
"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee." The following is a list of risks identified for this story, with assigned probability and impact.
- A. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
- B. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- C. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low - D. A small child may try to steam milk. Probability: High. Impact: Low
Answer: B
NEW QUESTION # 31
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. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.
- C. Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.
- D. 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.
Answer: D
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 # 32
You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?
- A. Ask experienced testers to prepare test charters for time boxed sessions lasting no more than 2hours.Tests should be designed and executed within each session using heuristics, creativity and intuition.
- B. Use testers who have not been involved in the sprint to write new test cases from the user stories. These test cases are then executed in a time boxed session for the sprint.
- C. Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.
- D. Allocate independent testers to design exploratory tests using test charters in time boxed sessions. Plan to run all sessions in parallel with each session lasting more than 5hours.
Answer: A
Explanation:
Explanation
Exploratory testing is a testing approach that emphasizes learning, creativity, and adaptability. It involves simultaneous test design and test execution, where the tester uses heuristics, intuition, and experience to explore the system under test and discover new information12. Exploratory testing can be performed in an Agile project to complement other testing activities, such as test-driven development, behavior-driven development, and acceptance test-driven development12.
The correct approach to adopt for exploratory testing in an Agile project is D, as it follows the best practices for exploratory testing1234:
Ask experienced testers to prepare test charters for time boxed sessions lasting no more than 2 hours: A test charter is a brief document that describes the scope, objective, and strategy of an exploratory testing session. A test charter helps to guide the tester's exploration and to document the results. A time box is a fixed period of time allocated for an exploratory testing session. A time box helps to focus the tester's attention and to limit the scope of exploration. A time box should not be too long, as it may reduce the tester's concentration and creativity. A recommended duration for a time box is between 45 minutes and
2 hours.
Tests should be designed and executed within each session using heuristics, creativity and intuition:
Exploratory testing is an iterative and interactive process, where the tester designs and executes tests based on the observations and feedback from the system under test. The tester uses heuristics, which are rules of thumb or shortcuts that help to simplify the testing problem and to generate test ideas. The tester also uses creativity and intuition, which are mental abilities that help to generate novel and useful solutions and to make judgments based on incomplete or uncertain information.
The incorrect approaches to adopt for exploratory testing in an Agile project are A, B, and C, as they violate the principles and practices of exploratory testing1234:
A: Allocate independent testers to design exploratory tests using test charters in time boxed sessions.
Plan to run all sessions in parallel with each session lasting more than 5 hours: This approach is incorrect because it does not involve simultaneous test design and test execution, which is the essence of exploratory testing. It also uses too long time boxes, which may reduce the tester's concentration and creativity. It also does not leverage the collaboration and communication within the Agile team, as it isolates the testers from the developers and other stakeholders.
B: Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools: This approach is incorrect because it does not use test charters, which are essential for guiding and documenting the exploratory testing sessions. It also does not use heuristics, creativity, and intuition, which are important for generating test ideas and making decisions. It also implies that exploratory testing is an unstructured and random activity, which is a common misconception. Exploratory testing is a disciplined and systematic approach that requires planning, analysis, and evaluation.
C: Use testers who have not been involved in the sprint to write new test cases from the user stories.
These test cases are then executed in a time boxed session for the sprint: This approach is incorrect because it does not involve simultaneous test design and test execution, which is the essence of exploratory testing. It also uses testers who have not been involved in the sprint, which may reduce their understanding of the system under test and the customer needs. It also does not use test charters, which are essential for guiding and documenting the exploratory testing sessions. It also does not use heuristics, creativity, and intuition, which are important for generating test ideas and making decisions.
References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 23; ISTQB Agile Tester Sample Exam2, question 19; Exploratory Testing; ISTQB Agile Tester #56 - What is Exploratory testing?
NEW QUESTION # 33
A calculator application is being developed. The third sprint has been planned to add functionality to the calculator to allow scientific calculations.
Which TWO examples below represent activities that would likely be managed on an agile task board for the third sprint?
1) A task to design the features planned for the next sprint.
2) A task to run an acceptance test for a user story.
3) A task to automate regression tests.
4) A task to participate in training in preparation for the fourth sprint.
5) A task to produce a daily progress report for the agile team members.
- A. 4, 5
- B. 2, 3
- C. 1, 4
- D. 1, 5
Answer: B
NEW QUESTION # 34
Consider the estimation of a given user story performed separately by two different teams (Team A and Team B) using the Planning Poker technique. Both teams consist of five members and use a deck of cards (0, 1, 2, 3, 5, 8, 13, 20).
Team A quickly decides on an estimate of8 story pointsafter four rounds, withno discussionsbetween rounds.
Team B arrives at3 story pointsafter three rounds, withdiscussionsbetween the lowest and highest estimators after each round.
Which of the following statements would you expect most likely to be true in this scenario?
- A. Team A has a better estimation process than Team B because at the end of the last round, all five team members' estimates are an exact match
- B. Both Team A and B have an ineffective estimation process because the best estimate is the average of the results of the first round of estimation
- C. In the estimation process, Team B, unlike Team A, can take advantage of the discussions that represent an important benefit of using Planning Poker
- D. Team B estimates that the user story can be "done" with significantly less effort in absolute terms than what was estimated by Team A
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.2Release and Iteration Planning, it describes Planning Poker as:
"Planning Poker involves group discussion, especially from the highest and lowest estimators, to ensure that different perspectives and assumptions are aligned, which leads to more accurate and shared understanding of the effort involved." Thus,Option Cis correct - Team B usesdiscussion-based estimation, which is a corebenefitof Planning Poker.
* Option Ais speculative - we cannot know the actual effort difference.
* Option Bis incorrect - convergence without discussion may indicatelack of engagement or pressure to agree.
* Option Dis false - Planning Poker isnot based on averaging, but onconsensus.
References:
CTFL-AT Syllabus v4.0, Section 2.2
Learning Objective (K2) - Understand the purpose and benefit of Planning Poker
NEW QUESTION # 35
In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.
The user story written on the card is:
"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email." By applying the 3C concept, which ONE of the following statements is CORRECT?
- A. The card should contain requirements not the user story.
- B. Conversation should include the acceptance criteria discussion.
- C. Product owner has written a user story and confirmation is not needed.
- D. The conversation is not required and the team should start developing.
Answer: B
NEW QUESTION # 36
Consider the following user story for an Agile project aimed at developing an application that calculates the reimbursement of medical visits:
"As an owner of the application, I want the reimbursement of medical visits to be calculated based on the following rules:
There are two types of reimbursable visits: Doctor's Office Visits (DOCVs) and Hospital Visits (HVs).
The reimbursement for DOCVs is 33%, while the reimbursement for HVs depends on the type of the specialist visits. Two types (A, B) of specialist visits exist and the associated reimbursements are 45% for A and 90% forB." Which of the following would you expect to be the most suitable black-box test design technique for the user story?
- A. State transition testing
- B. Decision table testing
- C. Use case testing
- D. Equivalence partition testing
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 3.1Testing Techniques and Agile, it states:
"Decision table testing is useful when the outcome depends on combinations of inputs or rules." In this case,different reimbursement percentagesare determined based ontypes of visits and subtypes, makingOption A (Decision Table Testing)the ideal technique.
* Option Bfocuses onsingle input ranges, less suitable here.
* Option Csuits end-to-end scenarios but not logic-driven calculations.
* Option Dapplies tostate-based systems, which this is not.
References:
CTFL-AT Syllabus v4.0, Section 3.1
Learning Objective (K3) - Apply appropriate test design techniques in Agile
NEW QUESTION # 37
You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.
The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.
A User Story for the Operator-Instructions module is as follows:
"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee." The following is a list of risks identified for this story, with assigned probability and impact.
- A. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
- B. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- C. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low - D. A small child may try to steam milk. Probability: High. Impact: Low
Answer: B
Explanation:
Risk-based testing is a technique that prioritizes testing activities based on the level of risk associated with each feature or requirement. The level of risk is usually calculated by multiplying the probability and impact of each risk. The higher the risk level, the more testing effort should be allocated to mitigate the risk. In this case, the risk level for each option is as follows: A. Risk level = Low x Low = Low B. Risk level = Low x High = Medium C. Risk level = High x High = High D. Risk level = High x Low = Medium Therefore, the highest risk level is C, followed by B and D, and then A. The User Story for the Operator-Instructions module should be tested according to this risk order, starting with C, then B, then D, and finally A. Hence, the answer is B, as it is the second highest risk level and should be tested after C. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 16; ISTQB Agile Tester Sample Exam2, question 18.
NEW QUESTION # 38
Which of the following is a typical task performed by a tester within a Scrum team?
- A. Prioritizing the items in the product backlog
- B. Coaching other team members in self-organization and cross-functionality
- C. Suggesting improvements in sprint retrospectives
- D. Removing impediments to the Scrum team's progress
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 5.1 and 5.3:
"Testers, like all team members, participate in retrospectives and are encouraged to suggest improvements to team processes and product quality." SoOption Ais correct. Testersactively engagein retrospectives andsuggest improvementsbased on their testing experience.
* Option BandCrefer toScrum Master responsibilities.
* Option Dis the responsibility of theProduct Owner.
References:
CTFL-AT Syllabus v4.0, Sections 5.1 and 5.3
Scrum Guide - Scrum Roles and Responsibilities
Learning Objective (K1) - Recall tester tasks within Scrum teams
NEW QUESTION # 39
Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?
- A. Developers write acceptance criteria and test cases, together with testers.
- B. Testers replace developers in writing unit test automation scripts.
- C. While developers develop automated unit test scripts, testers write automated system level tests.
- D. Developers and testers may work as a pair to develop and test a feature.
Answer: B
Explanation:
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 # 40
During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?
- A. For the last sprint the estimated and actual effort were much higher than the team capacity.
- B. The automation tests failed frequently without any logs to help in debugging the failure reason.
- C. The build process was slow and this often caused delays waiting for the build to complete.
- D. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.
Answer: D
Explanation:
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 # 41
In Agile projects, which of the following approaches would result in the best compromise for preserving independence of testers and for allowing testers to have a good understanding of the product as well as good relationships with other team members?
- A. Having independent separate test teams where testers are assigned to Agile teams on a long-term basis, at the beginning of an Agile project
- B. Having independent separate test teams where all of the testers work separately from developers without being assigned to Agile teams
- C. Having independent separate test teams where testers are assigned to Agile teams on-demand during the final days of each iteration
- D. Having only Agile teams where testers are integral parts and where they perform many of the testing tasks, without having an independent test team
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.5Testers and Independence, it states:
"Testers may be assigned to Agile teams on a permanent or rotating basis. While full independence is compromised, this setup allows for better collaboration and understanding of the product, while still maintaining some degree of independence." Thus,Option Bis the most accurate -long-term embedded testerssupport Agile collaboration while preservingpartial independence.
* Option Aleads tolate involvement, which contradicts Agile principles.
* Option Csacrifices independence entirely.
* Option Dis traditional and contrary to Agile values of collaboration.
References:
CTFL-AT Syllabus v4.0, Section 2.5
Learning Objective (K2) - Understand approaches to preserving test independence in Agile
NEW QUESTION # 42
Which of the following tools would you expect to be the most useful to report defects found during exploratory testing sessions in Agile projects?
- A. Tools that capture and log activities performed on an application during its use
- B. Continuous integration and build distribution tools
- C. Application lifecycle management (ALM) and task management tools
- D. Tools that generate data to populate an application's database
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 3.1Exploratory Testing:
"Exploratory testing benefits from tools that record tester activity, allowing the tester to reproduce and document issues found during unscripted testing sessions." Option Dis correct -activity capture toolshelp testerslog, replay, and reportfindings effectively in exploratory sessions.
* Option Ais for test data preparation, not reporting.
* Option Bis related to integration, not exploratory testing.
* Option Chelps track tasks but lacks session capture features.
References:
CTFL-AT Syllabus v4.0, Section 3.1
Learning Objective (K2) - Use appropriate tools during exploratory testing
NEW QUESTION # 43
Which of the following describes the main purpose of a task management tool in agile projects?
- A. A task management tool is used to manage and track user stories, tests and other tasks.
- B. A task management tool is used by team members to share ideas and collaborate on assigned tasks.
- C. A task management tool allows developers to continuously integrate their code.
- D. A task management tool is used to store source code and automated tests.
Answer: A
NEW QUESTION # 44
You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?
- A. Use testers who have not been involved in the sprint to write new test cases from the user stories. These test cases are then executed in a time boxed session for the sprint.
- B. Ask experienced testers to prepare test charters for time boxed sessions lasting no more than 2hours.
Tests should be designed and executed within each session using heuristics, creativity and intuition. - C. Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.
- D. Allocate independent testers to design exploratory tests using test charters in time boxed sessions. Plan to run all sessions in parallel with each session lasting more than 5hours.
Answer: B
NEW QUESTION # 45
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Acceptance Test-Driven Development
- B. Behavior-Driven Development
- C. Design-Driven Development
- D. Test-Driven Development
Answer: B
Explanation:
Behavior-Driven Development (BDD) is a software development approach that allows a developer to define accurate unit tests focused on business needs. BDD uses a common language that is understandable by both technical and non-technical stakeholders, such as Given-When-Then scenarios. BDD helps to align the development and testing activities with the customer expectations and business goals . 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
NEW QUESTION # 46
An Agile project is aimed at developing an e-commerce website that will allow registered users to purchase digital books. During the checkout process, only credit card payments, with supported credit card types, will be accepted.
Consider the following acceptance criterion for a given user story of this Agile project:
"Check that the number of steps required to complete a purchase order during the checkout process is minimized, in order to reduce the risk that the customers will leave the website without completing their orders." Which of the following information would you expect to be the most relevant to create a test aimed at covering this acceptance criterion?
- A. The maximum number of digital books that can be purchased in a single order
- B. The maximum number of steps to complete the checkout process
- C. The supported credit card types
- D. The maximum number of steps to complete the registration process
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.1Acceptance Criteria and Testability, it states:
"Tests should directly address the acceptance criteria defined for a user story. Testers evaluate if the implemented feature meets the criteria, often using quantitative data like number of steps, time taken, or interaction patterns." Theacceptance criterionspecifically refers tominimizing steps during checkout, soOption Dis most directly aligned with what needs to be tested.
* Options A, B, and Care unrelated to the acceptance criterion's goal of reducing abandonment due to complex checkout.
References:
CTFL-AT Syllabus v4.0, Section 2.1
Learning Objective (K2) - Understand testability of acceptance criteria
NEW QUESTION # 47
Which two of the following statements are CORRECT with regards to test automation on agile projects?
1) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.
2) It would be very difficult to ensure high quality in an agile project without test automation.
3) Automated acceptance tests are run regularly as part of the continuous integration full system build.
4) Automated regression suites are only run for the final release of code.
5) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.
- A. 2, 5
- B. 2, 3
- C. 3, 4
- D. 1, 3
Answer: A
Explanation:
Test automation is essential for agile projects, as it enables fast and frequent feedback on the quality of the product. Without test automation, it would be very difficult to ensure high quality in an agile project, as manual testing would be too slow and costly to keep up with the pace of development12. Automated acceptance tests are one of the key types of test automation on agile projects, as they verify that the user stories are implemented correctly and that the product meets the customer's expectations. Automated acceptance tests are run regularly as part of the continuous integration full system build, and the results provide feedback on the overall product quality12. Therefore, statements 2 and 5 are correct with regards to test automation on agile projects. 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
NEW QUESTION # 48
Which of the following is NOT a typical task performed by the tester within an Agile team?
- A. Ensuring all project status meetings are held according to the plan.
- B. Suggesting improvements in team retrospectives.
- C. Working with business stakeholders to clarify requirements.
- D. Ensuring the appropriate testing tasks are scheduled during iteration planning.
Answer: A
NEW QUESTION # 49
......
Updated CTFL-AT Dumps Questions Are Available For Passing ISQI Exam: https://www.dumpexams.com/CTFL-AT-real-answers.html
New CTFL-AT Dumps For Preparing Agile Tester Certified ISQI Exam Well: https://drive.google.com/open?id=17IYwaHW75pTQZPZDlqM_b3U2Ty3I61_F