Use Real CTFL-AT - 100% Cover Real Exam Questions [Dec-2025]
Dumps Brief Outline Of The CTFL-AT Exam - PassLeader
ISQI CTFL-AT (ISTQB Certified Tester - Foundation Level Extension - Agile Tester) Certification Exam is a globally recognized certification for professionals who want to enhance their knowledge and expertise in Agile methodology. ISTQB Certified Tester - Foundation Level Extension - Agile Tester certification is designed to provide an in-depth understanding of the Agile testing methodology, principles, and practices. It is an ideal certification for individuals who want to become proficient in Agile testing and want to advance their careers in this field.
The CTFL-AT exam is a three-hour, multiple-choice exam that consists of 40 questions. It covers various topics related to agile testing, such as agile testing techniques, agile testing methodologies, testing in agile projects, and tools and automation in agile testing. CTFL-AT exam is designed to test the candidate's knowledge and understanding of agile testing concepts and their ability to apply these concepts in real-world scenarios.
NEW QUESTION # 30
Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?
1) User access for all roles has been validated.
2) A static analysis tool has been executed for all code.
3) 100% of the existing regression test suite has passed.
4) System is responding in less than 3 seconds, 90% of the time.
5) A new version of internet Explorer has been included.
- A. 1, 3
- B. 4, 5
- C. 2, 5
- D. 3, 4
Answer: D
Explanation:
The acceptance criteria for a sprint are the conditions that must be met for the user stories to be considered done and deliver value to the customer1. The acceptance criteria should be specific, measurable, achievable, relevant, and testable2. In this case, the plan for the sprint is to increase performance of the system, so the acceptance criteria should reflect that goal. Therefore, the acceptance criteria that would be expected for Sprint 5 are:
* 100% of the existing regression test suite has passed. This criterion ensures that the system has not introduced any new defects or broken any existing functionality while improving performance3.
* System is responding in less than 3 seconds, 90% of the time. This criterion defines a clear and quantifiable performance target that can be verified by testing4.
The other options are not relevant or appropriate acceptance criteria for Sprint 5:
* User access for all roles has been validated. This criterion is not related to the performance of the system, but rather to the security or functionality of the system. It might be an acceptance criterion for a different sprint or user story, but not for Sprint 55.
* A static analysis tool has been executed for all code. This criterion is not a customer
NEW QUESTION # 31
During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?
- A. The automation tests failed frequently without any logs to help in debugging the failure reason.
- B. One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.
- C. For the last sprint the estimated and actual effort were much higher than the team capacity.
- D. The build process was slow and this often caused delays waiting for the build to complete.
Answer: B
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 process improvement, 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 # 32
Which of the following is NOT a statement of value from the Agile Manifesto?
- A. Customer collaboration over contract negotiation.
- B. Responding to change over following a plan.
- C. Working software over comprehensive documentation
- D. Processes and tools over individuals and interactions.
Answer: D
Explanation:
Explanation
The Agile Manifesto is a declaration of four values and twelve principles that guide the Agile software development approach12. The four values of the Agile Manifesto are12:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
These values emphasize the importance of human collaboration, working product, customer feedback, and adaptability over rigid processes, extensive documentation, fixedcontracts, and predefined plans. The values do not imply that the items on the right are not important, but rather that the items on the left are more important and should be prioritized.
Therefore, the statement that is NOT a value from the Agile Manifesto is B, as it contradicts the first value of the Agile Manifesto. The correct statement should be "Individuals and interactions over processes and tools". References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 1.
NEW QUESTION # 33
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Test-Driven Development
- B. Design-Driven Development
- C. Acceptance Test-Driven Development
- D. Behavior-Driven Development
Answer: D
Explanation:
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:
1: ISTQB Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2
2: ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2
NEW QUESTION # 34
Which one of the following is a testable acceptance criterion?
- A. The response time to confirm a customer submission must not exceed 5 seconds.
- B. The system shall be easy to use.
- C. The tools for testing are tested before use and are meeting the requirements.
- D. The solution shall support business processes.
Answer: A
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 # 35
Which of the following is NOT a statement of value from the Agile Manifesto?
- A. Customer collaboration over contract negotiation.
- B. Responding to change over following a plan.
- C. Working software over comprehensive documentation
- D. Processes and tools over individuals and interactions.
Answer: D
NEW QUESTION # 36
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. Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.
- C. 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.
- D. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.
Answer: C
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 # 37
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. Developers write acceptance criteria and test cases, together with testers.
- C. Developers and testers may work as a pair to develop and test a feature.
- D. Testers replace developers in writing unit test automation scripts.
Answer: D
NEW QUESTION # 38
Which ONE of the following is an example of a typical "Business-oriented work product"?
- A. Acceptance testing entry criteria.
- B. The released product.
- 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 # 39
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 the various skill sets within the team to be leveraged to the benefit of the project.
- C. Enables the team to focus on solely their separate areas of expertise and responsibility.
- D. Enables testers to execute their responsibility for quality for the combined team.
Answer: B
NEW QUESTION # 40
You are working in a software development company which, for many years, used a sequential development model and was organized into separate departments for each functional group (e.g. business analysts, developers, testers) located within their own office space. Your organization has recently changed to a SCRUM agile framework.Which of the following is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model?
- A. Co-located teamwork means that all team members, including developers and testers, must sit together in the same office, so they can quickly communicate face-to-face.
- B. Cross-functional teamwork means that all team members contribute to testing in various ways. For example, involving people with the test strategy, test planning and execution as well as test reporting.
- C. Credibility means that the tester must share information with the stakeholders about the test process so that they find the selected test strategy and testing activities trustworthy.
- D. Resilient testing means that the testing process is capable of dealing with rapid changes throughout the development process with test plans being updated during each iteration.
Answer: B
NEW QUESTION # 41
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. Payment for parking ticket is restricted to cash only (no credit card supported).
- 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. Price for a bus ticket was calculated incorrectly.
Answer: A
Explanation:
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 # 42
Which agile development approach incorporates the following practices:
* a project is divided into iterations called sprints
* each sprint results in a potentially releasable/shippable product?
- A. Scrum
- B. Continuous Integration
- C. Kanban
- D. Extreme Programming
Answer: A
NEW QUESTION # 43
What is the main benefit of the Test Pyramid?
- A. It acts as a metric for testing progress.
- B. It means testing is involved early in the development cycle.
- C. It shows complexity of testing activities.
- D. It helps in evaluating the amount of test cases needed.
Answer: D
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 # 44
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. Continuous integration and build distribution tools
- B. Application lifecycle management (ALM) and task management tools
- C. Tools that generate data to populate an application's database
- D. Tools that capture and log activities performed on an application during its use
Answer: D
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 # 45
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?
- A. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
- B. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- C. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
- D. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
Answer: A
NEW QUESTION # 46
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. User story testing - test that the user can enter an income amount and get a result.
- B. State transition testing - test all states of income entry.
- C. Equivalence partitioning - test with low, medium and high income.
- D. Statement testing - test all statements in income calculation.
Answer: C
Explanation:
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 # 47
Which of the following statements about the test pyramid is true?
- A. The test pyramid concept states that every software system consists always of four different test levels (unit, integration, system, acceptance)
- B. The test pyramid consists of four test levels with business-facing tests at the bottom of the pyramid and technology-facing tests at the top
- C. The test pyramid emphasizes having more automated tests at the higher test levels and a decreasing number of them at the lower test levels
- D. The test pyramid concept is based on the principle of eliminating defects as early as possible in the software lifecycle
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 4.1The Test Pyramid, it states:
"The test pyramid concept encourages more tests at lower levels (e.g., unit tests), with fewer tests at higher levels (e.g., system or UI tests), in order to find and fix defects as early as possible." Therefore,Option Ais correct - thetest pyramid supports early defect detectionthrougha high volume of lower-level automated tests.
* Option Bis incorrect - thetest pyramid emphasizes more tests at lower levels, not higher.
* Option Cis incorrect - Agile doesn't mandate four specific levels in every system.
* Option Dmisrepresents the pyramid -technology-facing tests (e.g., unit tests)areat the bottom, not the top.
References:
CTFL-AT Syllabus v4.0, Section 4.1
Learning Objective (K2) - Understand the purpose of the test pyramid
NEW QUESTION # 48
You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:
"IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customer's monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases, the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager." Which of the following test cases can be treated as acceptance test criteria for the above user story?
1) As a customer assistant I can log in to the system and check the history of the customer account for the last year.
2) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.
3) As a customer assistant I can log in to the system and change my password.
4) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.
5) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.
6) As a bank manager I can log in to the system within 10 seconds.
- A. Acceptance test criteria are 1, 2, 3 and 6
- B. Acceptance test criteria are 1, 2, 4 and 5
- C. Acceptance test criteria are 1, 3, 4 and 5
- D. Acceptance test criteria are 2, 4, 5 and 6
Answer: B
Explanation:
Acceptance test criteria are the conditions that a user story must satisfy to be accepted by the customer or the stakeholder. They are usually derived from the user story and its acceptance scenarios, and they should cover the functional and non-functional requirements of the user story. Acceptance test criteria should be clear, concise, testable, and agreed upon by the team and the customer or the stakeholder.
In this case, the user story describes the business rule for approving a loan request based on the customer's income, repayment history, and loan amount. The user story also specifies the roles of the customer assistant and the bank manager in the process. Therefore, the acceptance test criteria should verify that the user story is implemented correctly and that the system behaves as expected for different scenarios and inputs.
The following test cases can be treated as acceptance test criteria for the above user story:
* As a customer assistant I can log in to the system and check the history of the customer account for the last year. This test case verifies that the customer assistant can access the system and view the customer' s income information, which is one of the factors for approving the loan request.
* As a customer assistant I can log in to the system and check the history of the customer debts and repayments. This test case verifies that the customer assistant can access the system and view the customer's repayment history, which is another factor for approving the loan request.
* As a bank manager I can log in to the system and receive the information of all requests waiting for approval. This test case verifies that the bank manager can access the system and see the list of loan requests that have been prepared by the customer assistant, and that the system provides the necessary information for each request.
* As a bank manager I can log in to the system and decide whether to approve a loan for a customer. This test case verifies that the bank manager can access the system and perform the approval action for a loan request, and that the system applies the business rule correctly and updates the status of the request accordingly.
The following test cases cannot be treated as acceptance test criteria for the above user story:
* As a customer assistant I can log in to the system and change my password. This test case is not related to the user story, as it does not verify any of the functional or non-functional requirements of the user story. It is a generic test case that applies to any user of the system, not specific to the customer assistant role or the loan approval process.
* As a bank manager I can log in to the system within 10 seconds. This test case is not related to the user story, as it does not verify any of the functional or non-functional requirements of the user story. It is a performance test case that applies to any user of the system, not specific to the bank manager role or the loan approval process.
1: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.1, pages 15-16; ISTQB Glossary of Testing Terms2, version 4.0, pages 2 and 3.
NEW QUESTION # 49
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. 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.
- 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. 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.
Answer: B
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 # 50
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 # 51
......
Certification Training for CTFL-AT Exam Dumps Test Engine: https://examcertify.passleader.top/ISQI/CTFL-AT-exam-braindumps.html