[Q11-Q33] Pass Your CTFL-AT Exam Easily With 100% Exam Passing Guarantee [2024]

Q11. Which of the following statements about Agile retrospectives is CORRECT?

During Agile retrospectives, testers should be encouraged to provide constructive suggestions only on non-testing activities.

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.

Agile retrospectives should be focused mainly on impediments that are outside the control of the team because these issues are more challenging.

Unlike working sessions or meetings held in non-Agile projects, Agile retrospectives do not require follow-up activities.

Q12. 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?

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.

Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.

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.

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.

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?

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

The build process was slow and this often caused delays waiting for the build to complete.

For the last sprint the estimated and actual effort were much higher than the team capacity.

The automation tests failed frequently without any logs to help in debugging the failure reason.

One of the testers was regarded as being both disruptive and lazy and did not contribute to team success.

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.

Q14. Which of the following statements is FALSE regarding early and frequent feedback?

Early feedback decreases the amount of time needed for system testing.

Early feedback promotes early discovery and resolution of quality problems.

Early feedback provides the Agile team with information on its productivity.

Early feedback helps to deliver a product that better reflects what the customer wants.

Q15. Which of the following is NOT a typical task performed by the tester within an Agile team?

Ensuring all project status meetings are held according to the plan.

Ensuring the appropriate testing tasks are scheduled during iteration planning.

Suggesting improvements in team retrospectives.

Working with business stakeholders to clarify requirements.

Q16. You are a tester in an agile team. The user story you are due to test is still under development so your tests are blocked. The main issue holding progress on this user story is that the developer’s unit tests are constantly failing.
As an agile tester, which of the following actions should you take?

Review the design of the problematic user story and improve it where possible.

Create a bug report for each of your blocked tests.

Work together with the developer, suggesting reasons why the tests are failing.

Use the time to improve and automate existing test cases of other user stories.

Q17. 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?

Kanban

Extreme Programming

Continuous Integration

Scrum

Q18. 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.

3, 4

2, 5

1, 3

2, 3

Q19. 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?

Decision table testing. Test the following conditions:
Conditions=registered user logged in; inserted power of the vehicle=20kW; Action=Car tax paid

State transition testing. Test the transitions between the following states:
logging in, inserting the power of the vehicle, making payment, logging out.

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]

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

Q20. Which of the following would provide the MOST independence for testers working with agile teams?

Testers are fully embedded in each Agile team to perform many of the testing tasks.

Testers from an independent test team who do not get involved with the Agile team, but are assigned to do System Testing once all sprints are completed.

Testers from an independent test team are assigned on-demand for the final days of each sprint.

Testers from an independent test team are assigned to the Agile team at the beginning of the project, returning for re-assignment to a new agile team.

Q21. 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.

Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low

The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High

An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High

A small child may try to steam milk. Probability: High. Impact: Low

Q22. 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.

Acceptance test criteria are 1, 2, 3 and 6

Acceptance test criteria are 1, 3, 4 and 5

Acceptance test criteria are 2, 4, 5 and 6

Acceptance test criteria are 1, 2, 4 and 5

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.
References: 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.

Q23. Which one of the following is a testable acceptance criterion?

The solution shall support business processes.

The system shall be easy to use.

The response time to confirm a customer submission must not exceed 5 seconds.

The tools for testing are tested before use and are meeting the requirements.

Q24. What is the main benefit of the Test Pyramid?

It means testing is involved early in the development cycle.

It helps in evaluating the amount of test cases needed.

It shows complexity of testing activities.

It acts as a metric for testing progress.

Q25. 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.

2, 3

1, 4

4, 5

1, 5

Q26. Which of the following describes the main purpose of a task management tool in agile projects?

A task management tool is used by team members to share ideas and collaborate on assigned tasks.

A task management tool is used to manage and track user stories, tests and other tasks.

A task management tool is used to store source code and automated tests.

A task management tool allows developers to continuously integrate their code.

Q27. 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.

2, 3

1, 4

4, 5

1, 5

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.

Q28. 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?

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.

Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.

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.

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.

Q29. Which of the following is a risk that continuous integration introduces?

Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.

Testers sometimes have too many builds to test, which reduces the quality of testing.

Teams no longer have the ability to run manual tests, as all tests must be automated.

Developer’s workload is increased, which can result in a reduction of output.

Q30. Which of the following is a benefit of a whole-team approach?

Enables reduction in test duplication as the testers and test engineers function as a single team.

Enables testers to execute their responsibility for quality for the combined team.

Enables the team to focus on solely their separate areas of expertise and responsibility.

Enables the various skill sets within the team to be leveraged to the benefit of the project.

Q31. Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?

While developers develop automated unit test scripts, testers write automated system level tests.

Testers replace developers in writing unit test automation scripts.

Developers write acceptance criteria and test cases, together with testers.

Developers and testers may work as a pair to develop and test a feature.

Q32. 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.

3, 4

2, 5

1, 3

2, 3

Q33. 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.

2, 5

2, 4, 5

1, 3, 4

1, 3

[Q11-Q33] Pass Your CTFL-AT Exam Easily With 100% Exam Passing Guarantee [2024]

Leave a Reply Cancel reply