ISQI CTFL-AT Deluxe Study Guide with Online Test Engine
CTFL-AT dumps review - Professional Quiz Study Materials
The CTFL-AT exam is an extension of the ISTQB Certified Tester - Foundation Level (CTFL) certification program. The CTFL-AT certification is a recognition of the tester's ability to apply Agile principles and practices to software testing. CTFL-AT exam covers various topics such as Agile testing process, testing techniques in Agile projects, and Agile testing tools and methods.
ISQI CTFL-AT, also known as ISTQB Certified Tester - Foundation Level Extension - Agile Tester, is a certification exam designed for professionals who are looking to gain an understanding of Agile testing methodologies. CTFL-AT exam is intended to validate a candidate's skills and knowledge in Agile testing and provides an opportunity for individuals to enhance their career prospects in the field of software testing.
NEW QUESTION # 24
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, 4, 5
- C. 2, 5
- D. 1, 3, 4
Answer: B
NEW QUESTION # 25
Which of the following statements is FALSE regarding early and frequent feedback?
- A. Early feedback decreases the amount of time needed for system testing.
- B. Early feedback helps to deliver a product that better reflects what the customer wants.
- C. Early feedback provides the Agile team with information on its productivity.
- D. Early feedback promotes early discovery and resolution of quality problems.
Answer: A
Explanation:
Explanation
Early and frequent feedback is one of the core values of Agile development. It helps the Agile team to deliver features with the highest business value first, to discover and resolve quality problems as soon as possible, to provide information on the team's productivity and progress, and to ensure that the product meets the customer's expectations and needs. However, early feedback does not necessarily decrease the amount of time needed for system testing, as system testing is still an important activity in Agile projects to verify the integration and functionality of the whole system. Early feedback may reduce the number of defects found in system testing, but it does not eliminate the need for system testing. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 11.
NEW QUESTION # 26
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 1, 4 and 6
- B. Activities 2, 3 and 5
- C. Activities 2 and 4
- D. Activities 1, 3 and 6
Answer: D
NEW QUESTION # 27
Which of the following sentences related to Risk-based testing is CORRECT?
- A. Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.
- B. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
- C. Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.
- D. Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.
Answer: A
NEW QUESTION # 28
Which of the following would provide the MOST independence for testers working with agile teams?
- A. 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.
- B. 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.
- C. Testers from an independent test team are assigned on-demand for the final days of each sprint.
- D. Testers are fully embedded in each Agile team to perform many of the testing tasks.
Answer: A
Explanation:
Explanation
Independence in testing is the degree of separation between the person who tests something and the person who developed it. Independence can help to reduce bias, increase objectivity, and provide different viewpoints. However, independence also has some drawbacks, such as increased communication overhead, reduced collaboration, and delayed feedback. In agile projects, testers are usually embedded in the agile teams to perform many of the testing tasks, such as unit testing, integration testing, acceptance testing, etc. This provides a high level of collaboration and fast feedback, but also reduces the independence of the testers.
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, would provide the most independence for testers working with agile teams. However, this would also introduce many disadvantages, such as lack of alignment with the agile principles, loss of context and domain knowledge, delayed defect detection and resolution, and increased risk of missing customer expectations. References: ISTQB Foundation Level Agile Tester Syllabus, Section
1.1.2, page 8; ASTQB Agile Tester Certification Resources, Section 1.1.2, page 8.
NEW QUESTION # 29
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. 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] - C. State transition testing. Test the transitions between the following states:
logging in, inserting the power of the vehicle, making payment, logging out. - 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: B
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 # 30
Which of the following statements is FALSE regarding early and frequent feedback?
- A. Early feedback helps to deliver a product that better reflects what the customer wants.
- B. Early feedback promotes early discovery and resolution of quality problems.
- C. Early feedback decreases the amount of time needed for system testing.
- D. Early feedback provides the Agile team with information on its productivity.
Answer: D
NEW QUESTION # 31
Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?
- A. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
- B. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
- C. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.
- D. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
Answer: C
NEW QUESTION # 32
Which of the following is NOT a typical task performed by the tester within an Agile team?
- A. Ensuring the appropriate testing tasks are scheduled during iteration planning.
- B. Ensuring all project status meetings are held according to the plan.
- C. Working with business stakeholders to clarify requirements.
- D. Suggesting improvements in team retrospectives.
Answer: B
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 # 33
Which ONE of the following is an example of a typical "Business-oriented work product"?
- A. Usability testing test results.
- B. A user manual.
- C. Acceptance testing entry criteria.
- D. The released product.
Answer: C
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 tools for testing are tested before use and are meeting the requirements.
- C. The solution shall support business processes.
- D. The system shall be easy to use.
Answer: A
Explanation:
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 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. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- C. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
- D. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
Answer: D
NEW QUESTION # 36
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. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- C. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
- D. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
Answer: D
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 # 37
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 1, 4 and 6
- B. Activities 2, 3 and 5
- C. Activities 2 and 4
- D. Activities 1, 3 and 6
Answer: D
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 # 38
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.
- A. 2, 3, 4
- B. 1, 2, 5
- C. 1, 3, 4
- D. 2, 4, 5
Answer: C
Explanation:
Explanation
A test charter is a document that describes the scope, objective, and approach of an exploratory testing session.
It is used mainly in exploratory tests to guide the tester's actions and record the findings. A test charter may make reference to user stories, requirements, risks, or other sources of information that are relevant to the testing mission. A test charter also contains notes taken during a test session, such as test ideas, test results, bugs, issues, and observations. A test charter is not used to monitor a test process, as it is not a formal metric or report. It is also not used to outline the company test policy, as it is specific to a particular test session and context. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.2.3, page 18; ASTQB Agile Tester Certification Resources, Section 2.2.3, page 18; How to Write an Exploratory Test Charter, Creating an Exploratory Testing Charter, What is Exploratory Testing?.
NEW QUESTION # 39
What is the main benefit of the Test Pyramid?
- A. It shows complexity of testing activities.
- B. It helps in evaluating the amount of test cases needed.
- C. It acts as a metric for testing progress.
- D. It means testing is involved early in the development cycle.
Answer: C
NEW QUESTION # 40
Which of the following would provide the MOST independence for testers working with agile teams?
- A. 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.
- B. 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.
- C. Testers from an independent test team are assigned on-demand for the final days of each sprint.
- D. Testers are fully embedded in each Agile team to perform many of the testing tasks.
Answer: A
NEW QUESTION # 41
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. 1, 4
- B. 1, 5
- C. 4, 5
- 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 # 42
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. State transition testing - test all states of income entry.
- B. Statement testing - test all statements in income calculation.
- C. User story testing - test that the user can enter an income amount and get a result.
- D. Equivalence partitioning - test with low, medium and high income.
Answer: D
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 # 43
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. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low - B. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High
- C. A small child may try to steam milk. Probability: High. Impact: Low
- D. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High
Answer: B
Explanation:
Explanation
Risk-based testing is a technique that prioritizes testing activities based on the level of risk associated with each feature or requirement. The level of risk is usually calculated by multiplying the probability and impact of each risk. The higher the risk level, the more testing effort should be allocated to mitigate the risk. In this case, the risk level for each option is as follows:
A). Risk level = Low x Low = Low
B). Risk level = Low x High = Medium
C). Risk level = High x High = High
D). Risk level = High x Low = Medium
Therefore, the highest risk level is C, followed by B and D, and then A.
The User Story for the Operator-Instructions module should be tested according to this risk order, starting with C, then B, then D, and finally A.
Hence, the answer is B, as it is the second highest risk level and should be tested after C.
References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 16; ISTQB Agile Tester Sample Exam2, question 18.
NEW QUESTION # 44
What is the main benefit of the Test Pyramid?
- A. It shows complexity of testing activities.
- B. It helps in evaluating the amount of test cases needed.
- C. It acts as a metric for testing progress.
- D. It means testing is involved early in the development cycle.
Answer: B
Explanation:
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 # 45
Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?
- A. Developers write acceptance criteria and test cases, together with testers.
- B. While developers develop automated unit test scripts, testers write automated system level tests.
- 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
Explanation:
Explanation
Testers replace developers in writing unit test automation scripts. Comprehensive Explanation: The integration of development and testing activities in Agile projects is based on the principle of cross-functional teamwork, where all team members collaborate and share their skills and knowledge to achieve a common goal. In the context of testing, this means that testing is not seen as a separate activity or phase, but as an integral part of the development process. Therefore, the following sentences are correct:
While developers develop automated unit test scripts, testers write automated system level tests. This is an example of how developers and testers can work in parallel and complement each other's testing efforts. Developers can focus on testing the internal quality of the code, while testers can focus on testing the external quality of the product.
Developers write acceptance criteria and test cases, together with testers. This is an example of how developers and testers can work together to define and verify the user requirements and expectations.
Developers can provide their technical expertise and input, while testers can provide their business and user perspective and feedback.
Developers and testers may work as a pair to develop and test a feature. This is an example of how developers and testers can work closely and interactively to deliver a feature. Developers and testers can exchange ideas, suggestions, and information, and support each other in the coding and testing tasks.
The following sentence is incorrect:
Testers replace developers in writing unit test automation scripts. This is not a valid example of the integration of development and testing activities in Agile projects, because it implies that testers take over the responsibility of developers, rather than collaborate with them. Testers should not replace developers in writing unit test automation scripts, because developers have more knowledge and experience in coding and debugging, and because unit testing is an essential part of the development process. Testers should instead work with developers to ensure that the unit test automation scripts are adequate, effective, and maintainable. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Glossary of Testing Terms2, version 4.0, pages 16 and 55.
NEW QUESTION # 46
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. 1, 4
- B. 1, 5
- C. 4, 5
- D. 2, 3
Answer: D
NEW QUESTION # 47
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. Conversation should include the acceptance criteria discussion.
- B. Product owner has written a user story and confirmation is not needed.
- C. The card should contain requirements not the user story.
- D. The conversation is not required and the team should start developing.
Answer: A
NEW QUESTION # 48
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?
- A. The interface to External System shall be specified.
- B. The "ID" field must accept input value of a length between 2 and 10 characters.
- C. The program's icon should be clear and attractive.
- D. Action "Reopen" must be available only for a user with a specific authorization level.
Answer: D
NEW QUESTION # 49
......
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.
Exam Questions Answers Braindumps CTFL-AT Exam Dumps PDF Questions: https://www.testkingpdf.com/CTFL-AT-testking-pdf-torrent.html
CTFL-AT Test Prep Training Practice Exam Questions Practice Tests: https://drive.google.com/open?id=1S0Bebn9bAlu5YtvQOpR-FKvobEEKEp1x
