Pass Exam With Full Sureness – CTFL-AT Dumps with 40 Questions [Q19-Q38]

Q19. Which of the following allows a developer to define accurate unit tests focused on business needs?

Design-Driven Development

Behavior-Driven Development

Test-Driven Development

Acceptance Test-Driven Development

Q20. Which of the following is NOT a statement of value from the Agile Manifesto?

Working software over comprehensive documentation

Processes and tools over individuals and interactions.

Responding to change over following a plan.

Customer collaboration over contract negotiation.

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

Q22. Which of the following allows a developer to define accurate unit tests focused on business needs?

Design-Driven Development

Behavior-Driven Development

Test-Driven Development

Acceptance Test-Driven Development

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

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

Q25. Which of the following statements about a test charter are CORRECT?
1) It is used mainly in exploratory tests.
2) It is used to monitor a test process.
3) It may make reference to user stories.
4) It contains notes taken during a test session.
5) It is used to outline the company test policy.

1, 2, 5

2, 3, 4

2, 4, 5

1, 3, 4

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

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

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.

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.

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.

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.

Q28. Which of the following statements about a test charter are CORRECT?
1) It is used mainly in exploratory tests.
2) It is used to monitor a test process.
3) It may make reference to user stories.
4) It contains notes taken during a test session.
5) It is used to outline the company test policy.

1, 2, 5

2, 3, 4

2, 4, 5

1, 3, 4

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

Q30. Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?

Having at least once a day an automated build and test process that detects integration errors early and quickly.

Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.

Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.

Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.

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.

Q31. You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

The “ID” field must accept input value of a length between 2 and 10 characters.

The interface to External System shall be specified.

Action “Reopen” must be available only for a user with a specific authorization level.

The program’s icon should be clear and attractive.

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

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.

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.

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.

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.

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

Conversation should include the acceptance criteria discussion.

The card should contain requirements not the user story.

Product owner has written a user story and confirmation is not needed.

The conversation is not required and the team should start developing.

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

Q35. Why is regression of software a high risk in agile projects?

Test-driven development means that existing functionality is not considered.

Test automation can cause regression of software in the test environment.

Regression is built into software as a safeguard against unexpected failures.

There is code churn due to change in business needs over several sprints.

Q36. Which ONE of the following is an example of a typical “Business-oriented work product”?

The released product.

Acceptance testing entry criteria.

A user manual.

Usability testing test results.

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

Statement testing – test all statements in income calculation.

User story testing – test that the user can enter an income amount and get a result.

State transition testing – test all states of income entry.

Equivalence partitioning – test with low, medium and high income.

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

Statement testing – test all statements in income calculation.

User story testing – test that the user can enter an income amount and get a result.

State transition testing – test all states of income entry.

Equivalence partitioning – test with low, medium and high income.

Pass Exam With Full Sureness – CTFL-AT Dumps with 40 Questions [Q19-Q38]

Be the first to reply

Leave a Reply Cancel reply