NEW QUESTION 1
You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:
"IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customer's monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases, the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager."
Which of the following test cases can be treated as acceptance test criteria for the above user story?
1) As a customer assistant I can log in to the system and check the history of the customer account for the last year.
2) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.
3) As a customer assistant I can log in to the system and change my password.
4) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.
5) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.
6) As a bank manager I can log in to the system within 10 seconds.

• A. Acceptance test criteria are 1, 2, 3 and 6
• B. Acceptance test criteria are 1, 3, 4 and 5
• C. Acceptance test criteria are 2, 4, 5 and 6
• D. Acceptance test criteria are 1, 2, 4 and 5

Answer: D

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.

NEW QUESTION 2
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. The card should contain requirements not the user story.
• C. Product owner has written a user story and confirmation is not needed.
• D. The conversation is not required and the team should start developing.

Answer: A

Explanation:
The 3C concept of user stories consists of three elements: card, conversation, and confirmation12. The card is a written description of the user story that captures the essence of the feature or functionality from the user’s perspective. The conversation is a dialogue between the product owner and the development team to clarify the details, assumptions, and expectations of the user story. The confirmation is a set of criteria or tests that verify that the user story is implemented correctly and meets the user’s needs12. Therefore, by applying the 3C concept, the correct statement is A, as the conversation should include the acceptance criteria discussion. This will help the team to understand the scope, priority, and value of the user story, as well as the conditions of satisfaction that the product owner expects12. The other statements are incorrect, as they violate the 3C concept. Statement B is wrong, as the card should contain the user story, not the requirements. The user story is a brief and informal way of expressing the user’s goal and benefit, while the requirements are more detailed and specific descriptions of how
the software should work. The requirements can be added later as part of the conversation or confirmation12. Statement C is wrong, as the product owner has written a user story, but confirmation is still needed. The confirmation is a vital part of the 3C concept, as it ensures that the user story is testable, measurable, and verifiable. The confirmation also helps to avoid ambiguity, misunderstanding, or disagreement between the product owner and the development team12. Statement D is wrong, as the conversation is required and the team should not start developing without it. The conversation is an essential part of the 3C concept, as it allows the team to ask questions, share ideas, and collaborate with the product owner to refine the user story and reach a shared understanding. The conversation also helps to identify the dependencies, risks, and assumptions that may affect the implementation of the user story12. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.2.1, page 16-17; Effective User Stories - 3C’s and INVEST Guide2, Section The 3 C’s (Card, Conversation, Confirmation) of User Stories.

NEW QUESTION 3
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?

• A. Having at least once a day an automated build and test process that detects integration errors early and quickly.
• B. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
• C. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
• D. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.

Answer: C

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 4
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 analyzed twice- during release and iteration planning.
• B. Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.
• 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 fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.

Answer: D

Explanation:
Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories. User stories are short descriptions of features or functionalities that are valuable to the customers or users. They help to define the scope and priority of the work in each iteration. By breaking down the work into user stories, the Agile team can identify the potential risks associated with each story, such as technical complexity, business criticality, or user feedback. The team can then prioritize the testing effort based on the risk level of each story, ensuring that the most important and risky features are tested first and thoroughly. Risk-based testing also helps to optimize the testing time and resources, as the team can focus on testing the most relevant aspects of the software, rather than testing everything equally. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 181; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.2-1, page 92

NEW QUESTION 5
Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?

• A. Share the Test Strategy with the Agile development team, but not the details of the Test Cases.
• B. Locate the team that develops the test automation framework in a different location to the Agile development team.
• C. Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.
• D. Co-locate only some of the testers with the Agile development team, while the rest of the testers are in a different location.

Answer: C

Explanation:
According to the ISTQB Tester Foundation Level Agile Tester syllabus, one of the key principles of agile testing is that testers are integrated into the agile team and work closely with developers and other stakeholders. However, this does not mean that testers lose their independence or objectivity. Testers should still be able to provide an unbiased view of the quality of the software and challenge the assumptions and decisions made by the team. Therefore, option C is the best way for a test team to keep its independence when working in an agile development environment, as it allows testers to be part of the agile team, but also report to a different manager than the developers, who can support their professional development and ensure their independence. Option A is not a good way to keep independence, as it limits the transparency and collaboration between testers and developers, which are essential for agile testing. Option B is also not a good way to keep independence, as it creates a physical and organizational barrier between the test automation team and the agile development team, which can hinder communication and feedback. Option D is also not a good way to keep independence, as it creates an inconsistency and imbalance between the testers who are co-located with the agile development team and those who are not, which can affect the quality and efficiency of the testing process. References: ISTQB Tester Foundation Level Agile Tester syllabus, section 1.2.1, page 91; ISTQB Tester Foundation Level Agile Tester syllabus, section 1.2.2, page 101; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.1.1, page 141; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.1, page 161; ISTQB Tester Foundation Level Agile Tester syllabus, section 2.2.2, page 171.

NEW QUESTION 6
Which of the following is NOT a statement of value from the Agile Manifesto?

• A. Working software over comprehensive documentation
• B. Processes and tools over individuals and interactions.
• C. Responding to change over following a plan.
• D. Customer collaboration over contract negotiation.

Answer: B

Explanation:
The Agile Manifesto is a declaration of four values and twelve principles that guide the Agile software development approach12. The four values of the Agile Manifesto are12:
✑ Individuals and interactions over processes and tools
✑ Working software over comprehensive documentation
✑ Customer collaboration over contract negotiation
✑ Responding to change over following a plan
These values emphasize the importance of human collaboration, working product, customer feedback, and adaptability over rigid processes, extensive documentation, fixedcontracts, and predefined plans. The values do not imply that the items on the right are not important, but rather that the items on the left are more important and should be prioritized.
Therefore, the statement that is NOT a value from the Agile Manifesto is B, as it contradicts the first value of the Agile Manifesto. The correct statement should be “Individuals and interactions over processes and tools”. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 1.

NEW QUESTION 7
Which of the following sentences about the integration of development and testing activities
in Agile projects is INCORRECT?

• A. While developers develop automated unit test scripts, testers write automated system level tests.
• B. Testers replace developers in writing unit test automation scripts.
• C. Developers write acceptance criteria and test cases, together with testers.
• D. Developers and testers may work as a pair to develop and test a feature.

Answer: B

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 8
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 work
• B. Probability: Lo
• C. Impact: Low
• D. The instructions may be incorrect or appear in the wrong orde
• E. Probability: Lo
• F. Impact: High
• G. An untrained customer will attempt to use the coffee machin
• H. Probability: Hig
• I. Impact:High
• J. A small child may try to steam mil
• K. Probability: Hig
• L. Impact: Low

Answer: B

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 9
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. 1, 2, 5
• B. 2, 3, 4
• C. 2, 4, 5
• D. 1, 3, 4

Answer: D

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 10
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:
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 11
Which of the following statements about the Planning poker test estimate technique are CORRECT?
1) Planning poker is a consensus based technique using a deck of cards.
2) A low test estimate usually means the story should be broken down into multiple smaller stories.
3) A high test estimate usually means the story should be broken down into multiple smaller stories.
4) One poker round is played and then consensus has to be reached.
5) The risk level of each backlog item should be decided before the poker session.

• A. 1, 3, 5
• B. 1, 2, 3
• C. 2, 3, 4
• D. 1, 2, 4

Answer: A

Explanation:
Planning poker is a consensus-based technique for agile estimation, using a deck of cards with predefined numerical values, usually based on the Fibonacci sequence or a modified version12. Therefore, statement 1 is correct. A high test estimate usually means that the user story or task is too complex, ambiguous, or risky, and should be broken down into multiple smaller stories that are easier to understand and estimate13. Therefore, statement 3 is correct. The risk level of each backlog item should be decided before the poker session, as it can affect the estimation process and the prioritization of the work14. Therefore, statement 5 is correct. Statement 2 is incorrect, as a low test estimate usually means that the user story or task is simple, clear, and well-defined, and does not need to be broken down further13. Statement 4 is incorrect, as planning poker can involve multiple rounds of estimation, reveal, and discussion, until the team reaches a consensus or agrees to defer the item12. References: 1: ISTQB® Foundation Level Agile Tester Syllabus, Section 3.3.1, Test Automation1; 2: ASTQB Agile Tester Certification Resources, Section 3.3.1, Test Automation2; 3: Planning Poker: An Agile Estimating and Planning Technique3; 4: Planning poker: The all-in strategy for Agile estimation - Asana4

NEW QUESTION 12
Which of the following allows a developer to define accurate unit tests focused on business needs?

• A. Design-Driven Development
• B. Behavior-Driven Development
• C. Test-Driven Development
• D. Acceptance Test-Driven Development

Answer: B

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:
✑ : ISTQB® Foundation Level Agile Tester Syllabus, Version 2014, Section 2.2.2
✑ : ASTQB Agile Tester Certification Resources, Agile Testing Foundations, Chapter 3, Section 3.2.2

NEW QUESTION 13
......