Free Sample Questions to Practice CTFL-AT Certification Test Engine [May-2024]
2024 Valid CTFL-AT Real Exam Questions, practice Agile Tester
The CTFL-AT exam is an extension of the ISTQB Foundation Level certification program. CTFL-AT exam is designed to provide a comprehensive understanding of Agile testing concepts, including Agile software development process, testing in Agile projects, testing techniques, and tools. ISTQB Certified Tester - Foundation Level Extension - Agile Tester certification program is designed to help professionals gain a competitive edge in their career by showcasing their expertise in Agile testing methodologies.
NEW QUESTION # 23
Why is regression of software a high risk in agile projects?
- A. There is code churn due to change in business needs over several sprints.
- B. Test-driven development means that existing functionality is not considered.
- C. Test automation can cause regression of software in the test environment.
- D. Regression is built into software as a safeguard against unexpected failures.
Answer: A
Explanation:
Explanation
Regression of software is the risk that a change in one part of the software causes a defect in another part of the software that was previously working correctly. Regression of software is a high risk in agile projects because there is code churn due to change in business needs over several sprints. Code churn is the amount of code that is added, modified, or deleted in a software project over time. Code churn can indicate the volatility and complexity of the software, and the frequency and magnitude of the changes. In agile projects, code churn can be high because the business needs and the user requirements can change rapidly and frequently over several sprints, which are short iterations of development and testing. This means that the software is constantly evolving and adapting to the changing needs, and that the existing functionality and quality may be affected by the new or modified code. Therefore, regression of software is a high risk in agile projects, and it requires effective testing strategies and techniques to prevent, detect, and fix the regression defects. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.2, page 17; ISTQB Glossary of Testing Terms2, version 4.0, pages 36 and 55
NEW QUESTION # 24
Which of the following statements is FALSE regarding early and frequent feedback?
- A. Early feedback provides the Agile team with information on its productivity.
- B. Early feedback decreases the amount of time needed for system testing.
- C. Early feedback helps to deliver a product that better reflects what the customer wants.
- D. Early feedback promotes early discovery and resolution of quality problems.
Answer: A
NEW QUESTION # 25
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. 1, 5
- C. 1, 4
- D. 2, 3
Answer: D
Explanation:
Explanation
According to the ISTQB Tester Foundation Level Agile Tester syllabus, an agile task board is a visual tool that displays the status of the work items in an agile sprint. The task board typically shows the user stories, tasks, and their progress from "to do" to "done". The task board helps the agile team to monitor and coordinate their work, and to communicate with stakeholders. Therefore, the examples that represent activities that would likely be managed on an agile task board for the third sprint are those that are related to the user stories, tasks, and their progress in the current sprint. Option A is the correct answer, as it contains two examples of such activities: running an acceptance test for a user story, and automating regression tests. These are both tasks that are part of the testing process in the current sprint, and their status can betracked on the task board. Option B is not a correct answer, as it contains two examples of activities that are not related to the current sprint:
designing the features planned for the next sprint, and participating in training in preparation for the fourth sprint. These are both activities that are part of the planning or learning process for the future sprints, and they are not managed on the task board. Option C is also not a correct answer, as it contains two examples of activities that are not related to the current sprint: participating in training in preparation for the fourth sprint, and producing a daily progress report for the agile team members. These are both activities that are part of the learning or reporting process, and they are not managed on the task board. Option D is also not a correct answer, as it contains two examples of activities that are not related to the current sprint: designing the features planned for the next sprint, and producing a daily progress report for the agile team members. These are both activities that are part of the planning or reporting process, and they are not managed on the task board. 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 # 26
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:
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 # 27
Which tasks are typically performed by a tester on an Agile project?
1) Implementing test strategy.
2) Documenting business requirements.
3) Measuring and reporting test coverage.
4) Coaching development team in relevant aspects of testing.
5) Executing test-driven development tests.
- A. 1, 3
- B. 2, 5
- C. 1, 3, 4
- D. 2, 4, 5
Answer: C
Explanation:
Explanation
A tester on an Agile project typically performs the following tasks12:
Implementing test strategy: A tester helps to define and implement the test strategy for the Agile project, which includes the test approach, test levels, test types, test techniques, test tools, test environment, test data, test metrics, and test documentation.
Measuring and reporting test coverage: A tester measures and reports the test coverage of the product features and quality attributes, such as functionality, usability, performance, security, etc. Test coverage can be expressed in terms of test cases, test scenarios, test sessions, test conditions, test data, code, etc.
Coaching development team in relevant aspects of testing: A tester coaches the development team in relevant aspects of testing, such as test design, test execution, test automation, test-driven development, behavior-driven development, exploratory testing, etc. A tester also helps the development team to improve their testing skills and practices.
The following tasks are not typically performed by a tester on an Agile project:
Documenting business requirements: Business requirements are usually documented by the product owner or the business analyst, not by the tester. The tester may review and provide feedback on the business requirements, but the tester is not responsible for documenting them.
Executing test-driven development tests: Test-driven development tests are usually executed by the developers, not by the tester. The tester may assist the developers in creating and reviewing the test-driven development tests, but the tester is not responsible for executing them.
Therefore, the correct answer is C, as it contains the tasks that are typically performed by a tester on an Agile project. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, pages 14-15, 18-19, 22-23; ISTQB Agile Tester Sample Exam2, question 17.
NEW QUESTION # 28
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Test-Driven Development
- B. Behavior-Driven Development
- C. Acceptance Test-Driven Development
- D. Design-Driven Development
Answer: C
NEW QUESTION # 29
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?
- A. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
- B. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
- C. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
- D. Having at least once a day an automated build and test process that detects integration errors early and quickly.
Answer: B
Explanation:
Explanation
The whole-team approach is a principle of agile testing that involves everyone with different knowledge and skills to ensure project success. The whole-team approach means that the business representatives, testers, and developers work together in every step of the development process, from planning to delivery. The whole-team approach aims to enhance communication and collaboration within the team, leverage the various skill sets of the team members, and make quality everyone's responsibility12. Therefore, the statement C is the most direct advantage of the whole-team approach, as it captures the essence of the principle and its benefits.
The other statements are not directly related to the whole-team approach, or are incorrect. Statement A is about continuous integration, which is a practice of agile development that involves having at least once a day an automated build and test process that detects integration errors early and quickly. Continuous integration is not a direct consequence of the whole-team approach, although it may be facilitated by it13. Statement B is about avoiding requirements misunderstandings, which may be a benefit of the whole-team approach, but not the most direct one. The whole-team approach does not only focus on requirements, but also on design, implementation, testing, and delivery. Moreover, avoiding requirements misunderstandings may also depend on other factors, such as the quality of the user stories, the use of acceptance criteria, and the feedback from the customers and users14. Statement D is incorrect, as it contradicts the whole-team approach. The whole-team approach does not reduce the involvement of business representatives, but rather increases it.
Business representatives are an integral part of the whole-team approach, as they provide the vision, the value, and the validation of the product. They collaborate with the testers and developers to define the features, prioritize the backlog, and verify the outcomes12. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; What is Whole Team Approach in Agile Testing?2, Section What is Whole Team Approach?; Continuous Integration3, Section What is Continuous Integration?; Effective User Stories -
3C's and INVEST Guide4, Section The 3 C's (Card, Conversation, Confirmation) of User Stories.
NEW QUESTION # 30
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: D
NEW QUESTION # 31
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. Functional Testing
- C. Performance Testing
- D. Prototype Testing
Answer: A
NEW QUESTION # 32
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. 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.
- 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. 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.
Answer: D
Explanation:
Explanation
Cross-functional teamwork 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. Cross-functional teamwork means that all team members, regardless of their functional roles, 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. All team members contribute to testing in various ways, such as:
Involving people with the test strategy, test planning and execution as well as test reporting. This can help ensure that the testing activities are aligned with the business objectives, the user needs, and the technical requirements. It can also help improve the test coverage, the test quality, and the test efficiency.
Sharing the responsibility for testing among the team members. This can help reduce the workload and the dependency on a single tester or a testing team. It can also help increase the feedback and the communication among the team members, and foster a culture of quality and learning.
Leveraging the diverse skills and perspectives of the team members. This can help enhance the test design and the test execution by applying different techniques, tools, and approaches. It can also help identify and address the risks, the issues, and the opportunities for improvement from various angles. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Glossary of Testing Terms2, version 4.0, page 16.
NEW QUESTION # 33
Which of the following is NOT a statement of value from the Agile Manifesto?
- A. Processes and tools over individuals and interactions.
- B. Working software over comprehensive documentation
- C. Responding to change over following a plan.
- D. Customer collaboration over contract negotiation.
Answer: A
NEW QUESTION # 34
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. Payment for parking ticket is restricted to cash only (no credit card supported).
- C. Failed to buy a bus ticket when the network connection to the Central System is down.
- D. Failed to buy a bus ticket after 18:00.
Answer: B
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 # 35
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. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low - C. A small child may try to steam milk. Probability: High. Impact: Low
- D. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
Answer: D
NEW QUESTION # 36
Which of the following statements about Agile retrospectives is CORRECT?
- A. 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.
- B. During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities.
- C. Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.
- D. Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.
Answer: A
Explanation:
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 tasks are typically performed by a tester on an Agile project?
1) Implementing test strategy.
2) Documenting business requirements.
3) Measuring and reporting test coverage.
4) Coaching development team in relevant aspects of testing.
5) Executing test-driven development tests.
- A. 1, 3
- B. 2, 5
- C. 1, 3, 4
- D. 2, 4, 5
Answer: D
NEW QUESTION # 38
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. Product owner has written a user story and confirmation is not needed.
- B. The card should contain requirements not the user story.
- C. The conversation is not required and the team should start developing.
- D. Conversation should include the acceptance criteria discussion.
Answer: D
NEW QUESTION # 39
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
NEW QUESTION # 40
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Behavior-Driven Development
- B. Test-Driven Development
- C. Acceptance Test-Driven Development
- D. Design-Driven Development
Answer: A
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 # 41
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 # 42
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 testing. Test the following conditions:
Conditions=registered user logged in; inserted power of the vehicle=20kW; Action=Car tax paid - B. State transition testing. Test the transitions between the following states:
logging in, inserting the power of the vehicle, making payment, logging out. - C. Equivalence partitioning. 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] - D. 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:
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:
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: 3
NEW QUESTION # 43
Which of the following activities are done in release planning?
1) Identifying testable user stories with acceptance criteria.
2) Elaborating the user stories into tasks.
3) Prioritizing the user stories.
4) Creating acceptance tests for the user stories.
5) Analyzing risks for each of the user stories.
6) Performing high level estimation for the release.
- A. Activities 2 and 4
- B. Activities 2, 3 and 5
- C. Activities 1, 3 and 6
- D. Activities 1, 4 and 6
Answer: C
Explanation:
Explanation
Release planning is a process of defining the scope and timeline for an iterative or incremental product development project. It is used in agile or hybrid projects where a mid- to long-term planning of the product or system development or integration is required12. Release planning involves the following activities:
Identifying testable user stories with acceptance criteria. User stories are short descriptions of the features or functionalities that the customer or user wants from the product. Acceptance criteria are the conditions that must be met for the user story to be considered done and acceptable. Identifying testable user stories with acceptance criteria helps to define the scope and quality of the release13.
Prioritizing the user stories. User stories are prioritized based on the value they deliver to the customer or user, as well as the dependencies, risks, and costs associated with them. Prioritizing the user stories helps to determine the order and frequency of the releases13.
Performing high level estimation for the release. High level estimation is a technique to estimate the effort, time, and resources needed to complete the user stories in the release. High level estimation can be done using various methods, such as analogy, expert judgment, planning poker, etc. Performing high level estimation for the release helps to set realistic and achievable goals and deadlines13.
Therefore, activities 1, 3 and 6 are done in release planning. Activities 2, 4 and 5 are done in iteration planning, which is a more detailed and short-term planning of the work to be done in each iteration or sprint13. References: 1: ISTQB Foundation Level Agile Tester Syllabus, Section 2.2, Fundamental Agile Testing Principles, Practices and Processes1; 2: Agile Release Planning in Hybrid and Agile Projects4; 3: How to Create an Agile Release Plan5
NEW QUESTION # 44
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. 1, 5
- C. 1, 4
- D. 2, 3
Answer: D
NEW QUESTION # 45
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. Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.
- C. 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.
- 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: 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 # 46
Which of the following is NOT a typical task performed by the tester within an Agile team?
- A. Working with business stakeholders to clarify requirements.
- B. Ensuring the appropriate testing tasks are scheduled during iteration planning.
- C. Suggesting improvements in team retrospectives.
- D. Ensuring all project status meetings are held according to the plan.
Answer: D
Explanation:
Explanation
The tester within an Agile team is not responsible for ensuring all project status meetings are held according to the plan. This is typically a task for the Scrum Master, who facilitates the meetings and ensures that the team follows the Agile principles and practices. The tester within an Agile team is responsible for ensuring the appropriate testing tasks are scheduled during iteration planning, suggesting improvements in team retrospectives, and working with business stakeholders to clarify requirements. These are all tasks that contribute to the quality of the software and the testing process, as well as the collaboration and communication within the team and with the customers. 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-1, page 82
NEW QUESTION # 47
......
Genuine CTFL-AT Exam Dumps Free Demo Valid QA's: https://www.trainingquiz.com/CTFL-AT-practice-quiz.html
Latest Success Metrics For Actual CTFL-AT Exam (Updated 40 Questions): https://drive.google.com/open?id=1jBxmroojPy282fPFaiFwE8Lz67TC3m2j
