ISTQB ISTQB ATTA PDF ISTQB ISTQB ATTA PDF Questions Available Here at: https://www.certification-exam.com/en/dumps/istqb-exam/atta-dumps/quiz.html Enrolling now you will get access to 222 questions in a unique set of ISTQB ATTA Question 1 What is the value of statement coverage achieved by test case 1 from test set A? 2 credits [K3] Options: A. ? 75% (21/28) B. ? 78% (22/28) C. ? 85% (24/28) D. ? 90% (25/28) Answer: A Explanation: The correct answer is A. 75% (21/28). Statement coverage measures how many executable statements in the program are executed by a test case, compared to the total number of executable statements. The formula is: Statement coverage = (Number of executed statements / Total number of statements) x 100 For test case 1 from test set A: - Executed statements = 21 - Total statements = 28 So: (21 / 28) x 100 = 75% Therefore, test case 1 from test set A achieves 75% statement coverage, which corresponds to option A. Question 2 Which additional set of test cases is needed to achieve both 100% statement coverage and 100% decision coverage? 3 credits [K3] ISTQB ISTQB ATTA PDF https://www.certification-exam.com/ Options: A. B. C. D. Answer: C Explanation: The correct answer is C. To determine which additional set of test cases is needed, we need to look at the goal of achieving both: 1. 100% statement coverage 2. 100% decision coverage Statement coverage means that every executable statement in the code is executed at least once. Decision coverage means that every decision point in the code must evaluate to both: - true - false The key idea is that some test sets may execute all statements but still not exercise both outcomes of a decision. Others may cover both decision outcomes but miss some statements. Since the correct answer is C, that set of test cases is the one that complements the existing tests by: - executing any statements not yet covered - forcing each relevant condition or branch to take both outcomes at least once Why the other options are not correct: - A, B, and D do not provide the necessary combination of branch outcomes and statement execution needed to satisfy both coverage criteria together. - Only C adds the missing cases required to complete both statement and decision coverage. In short: C is correct because it is the only additional test set that ensures every statement is executed and every decision is exercised in both directions. Question 3 Which TWO additional structure-based test design techniques could be used to dynamically test the code? 1 credit [K2] Options: A. Condition testing B. Multiple condition testing C. Equivalence partitioning D. Cause/effect graphing ISTQB ISTQB ATTA PDF https://www.certification-exam.com/ E. Code reviews Answer: A, B Explanation: The correct answers are A. Condition testing and B. Multiple condition testing. This question asks for additional structure-based test design techniques that can be used to dynamically test code. Structure-based testing, also called white-box testing, is based on the internal structure of the software, such as code logic, branches, and conditions. Since the question asks for techniques that can be used dynamically, we are looking for techniques applied during execution of the code rather than static analysis. Why A is correct: Condition testing Condition testing is a structure-based technique focused on testing individual boolean expressions and their subconditions within decision points. It is used dynamically because the code is executed with specific inputs to verify the behavior of conditions. Why B is correct: Multiple condition testing Multiple condition testing extends condition testing by testing all possible combinations of conditions in a decision. Like condition testing, it is dynamic and structure-based because it requires executing the code under different combinations of input values to observe the outcomes. Why C is incorrect: Equivalence partitioning Equivalence partitioning is a specification-based technique, not structure-based. It divides input data into groups expected to behave similarly, based on requirements rather than code structure. Why D is incorrect: Cause/effect graphing Cause/effect graphing is also specification-based. It models relationships between inputs and outputs from the requirements perspective, not the internal code structure. Why E is incorrect: Code reviews Code reviews are static testing techniques. They examine the code without executing it, so they are not dynamic test design techniques. Summary: The two additional structure-based dynamic test design techniques are: A. Condition testing B. Multiple condition testing Question 4 How many test cases are needed to test code fragment lines 26 – 32 to achieve 100% condition determination coverage? 2 credits [K3] Options: A. 2 B. 3 C. 4 ISTQB ISTQB ATTA PDF https://www.certification-exam.com/ D. 5 Answer: B Explanation: To answer this, we need to understand what 100% condition determination coverage means. Condition determination coverage requires: 1. Every individual condition in the decision to evaluate to both true and false at least once. 2. The overall decision outcome to take both possible results at least once. For a code fragment with multiple conditions across lines 26–32, you usually need enough test cases to make each condition independently affect the result. If the logic contains two binary conditions combined in a decision, the minimum number of test cases is often 3: - one test where the decision is true, - one test where the decision is false, - and one additional test to make sure each individual condition has been exercised in both outcomes. Why not 2? Two tests can sometimes cover true and false outcomes of the decision, but they may not be enough to force every condition to independently evaluate both ways. Why 3 is correct: With three test cases, you can typically arrange inputs so that: - Test 1 makes one condition true and the decision true, - Test 2 makes one condition false and the decision false, - Test 3 exercises the remaining condition outcome needed for full condition determination coverage. So the correct answer is: B. 3 If you want, I can also show a simple example of how 3 test cases achieve this coverage. Question 5 The application of multiple condition testing is also being considered. Which specification-based technique is largely based on the principle of multiple condition testing? 1 credit [K2] Options: A. Equivalence Partitioning B. State Transition Testing C. Decision Table Testing D. Use Cases Answer: C Explanation: The correct answer is C. Decision Table Testing. Multiple condition testing focuses on checking combinations of different conditions to make sure the system ISTQB ISTQB ATTA PDF https://www.certification-exam.com/ behaves correctly for each possible combination. This is especially useful when the outcome depends on several inputs or rules at the same time. Decision table testing is a specification-based technique that is built around this idea. It lists: - the conditions, - the possible combinations of those conditions, - and the expected actions or outputs for each combination. This makes it a natural fit for multiple condition testing, because it helps ensure that all relevant combinations are covered systematically. Why the other options are not correct: A. Equivalence Partitioning This divides input data into groups where the system is expected to behave similarly. It does not primarily focus on combinations of multiple conditions. B. State Transition Testing This checks how the system moves from one state to another based on events or inputs. It is based on states and transitions, not condition combinations. D. Use Cases Use cases describe how users interact with the system to achieve goals. They are useful for functional testing, but they are not specifically based on multiple condition combinations. So, since decision tables are largely based on testing combinations of conditions and their resulting actions, the correct answer is C. Decision Table Testing. Question 6 How many test cases are needed to test code fragment lines 26 – 32 to achieve 100% multiple condition coverage? 2 credits [K3] Options: A. 2 B. 3 C. 4 D. 8 Answer: D Explanation: The correct answer is D. 8. Multiple condition coverage requires that every possible combination of the individual conditions in a decision be tested at least once. For a code fragment with 3 independent boolean conditions, each condition can be either true or false. That gives: 2 x 2 x 2 = 8 possible combinations So, to achieve 100% multiple condition coverage, you need 8 test cases. ISTQB ISTQB ATTA PDF https://www.certification-exam.com/ Why not the other options? A. 2 This would only cover a very small number of outcomes, not all combinations. B. 3 This is still not enough to cover all true/false combinations of 3 conditions. C. 4 This could be enough for condition coverage or branch coverage in some cases, but not multiple condition coverage. D. 8 This is correct because all 2^3 combinations must be tested. General rule: If there are n binary conditions, multiple condition coverage requires 2^n test cases. So for 3 conditions: 2^3 = 8 Hence, the answer is D. 8. Question 7 The Bonus Program is perceived by management to be critical. Defects in the program would almost immediately lead to financial loss. In the past an improvement program has been run to implement review based on IEEE 1028. Knowledge and skills on both formal and informal reviews are available. There is also an existing pool of review leaders. Which of the following review types would you choose to review the program? 2 credits [K4] Options: A. Informal review B. Inspection C. Walkthrough D. Management review Answer: B Explanation: The correct answer is B. Inspection. This question is asking which review type is most appropriate for a highly critical program where defects could quickly cause financial loss. Why inspection is the best choice: - Inspections are the most formal and rigorous type of review. - They are used when the quality risk is high and defects must be found as early and thoroughly as possible. - They follow a structured process, typically involving trained roles such as moderator, author, reader, and reviewer. ISTQB ISTQB ATTA PDF https://www.certification-exam.com/ - Since the organization already has: - knowledge and skills in formal and informal reviews - an existing pool of review leaders this means they are prepared to conduct a formal inspection effectively. Why not the other options: A. Informal review - Too lightweight for a critical financial program. - Informal reviews are useful for quick feedback, but they are not thorough enough when defects have major business impact. C. Walkthrough - A walkthrough is more structured than an informal review, but still less rigorous than an inspection. - It is often led by the author and is better for learning, understanding, or early feedback rather than maximum defect detection. D. Management review - A management review focuses on project progress, compliance, resources, and risk. - It is not primarily intended to detect defects in the program itself. Conclusion: Because the program is highly critical and defects would cause immediate financial loss, the most appropriate review type is the most formal and defect-focused one: inspection. Answer: B. Inspection Question 8 You have tested the program and have found that with “bonus” a boundary value has not been implemented according to design. You have written an incident report. Which of the following is the incident report of the highest quality? 2 credits [K3] Options: A. Description: Boundary value not correctly implemented Priority: High Repeatability: Yes Tester: WVU Test case: 35 (test specification “bonus program”), V1.2 B. Description: Boundary value not correctly implemented for bonus Priority: Medium Tester: WVU Test case: 35 (test specification “bonus program”) C. Description: Boundary value not correctly implemented for bonus (line 26: 10 according to design, now 5 implemented) Priority: High Repeatability: Yes Tester: WVU Test case: 35 (test specification “bonus program”), V1.2 D. Description: Boundary value not correctly implemented for bonus Priority: High Repeatability: Yes Tester: WVU Test case: 35 (test specification “bonus program”), V1.2 Answer: C Explanation: ISTQB ISTQB ATTA PDF https://www.certification-exam.com/ The correct answer is C. Why C is the highest-quality incident report: A good incident report should be clear, specific, and complete. It should let the developer quickly understand: - what went wrong, - where it went wrong, - how serious it is, - whether it can be reproduced, - and enough detail to locate and fix the problem. Option C does this best because it includes: - Description of the problem: “Boundary value not correctly implemented for bonus” - Precise location or evidence: “line 26: 10 according to design, now 5 implemented” - Priority: High - Repeatability: Yes - Tester identification: WVU - Test case reference: 35 - Test specification reference: “bonus program” - Version: V1.2 This is more useful than the other options because it gives concrete information about the defect, not just a vague statement. Why the other options are weaker: A. “Boundary value not correctly implemented” - Too vague. - It does not say for which feature or input. - It lacks specific defect details, so it is harder to reproduce and fix. B. “Boundary value not correctly implemented for bonus” - Better than A because it identifies the feature. - Still missing priority details that match seriousness. - No version information. - No precise defect detail, so it is incomplete. D. “Boundary value not correctly implemented for bonus” - Same vague description as B. - Although it includes High, Repeatability, tester, test case, and version, it still lacks the key technical detail about the actual expected value versus implemented value. - Without that, the report is less helpful for debugging than C. Conclusion: C is the best incident report because it is the most specific, complete, and actionable. It gives both the defect description and the exact mismatch between design and implementation, which makes it the highest-quality report. Question 9 Part 3 "Bonus Program" ISTQB ISTQB ATTA PDF https://www.certification-exam.com/ When performing code reviews, which of the following defect types will be most difficult to find? 1 credit [ Options: A. Dead code B. Variable used that is not defined C. Memory issues D. Conformance to design Answer: C Explanation: The correct answer is C. Memory issues. Code reviews are very good at finding defects that can be seen directly in the source code, especially if the reviewer has enough time and the code is clear. However, some defect types are much harder to detect by inspection alone. Why C is correct: Memory issues, such as memory leaks, dangling pointers, buffer overflows, or improper allocation and deallocation, are often difficult to identify during a code review because: - They may depend on runtime behavior. - They may only appear under certain input conditions or execution paths. - They can be subtle and require execution, debugging, or specialized analysis tools to detect reliably. Why the other options are easier to find: A. Dead code This is often easy to spot during a review because unused or unreachable code is visible in the source. B. Variable used that is not defined This is usually straightforward to detect, and many compilers or static analysis tools will flag it immediately. D. Conformance to design Reviewers can compare the code against design documents or requirements, so this is commonly checked during reviews. Conclusion: Code reviews are strongest at finding visible logic, style, and requirement-related issues, but memory issues often require dynamic testing or automated analysis tools. Therefore, C is the most difficult defect type to find during a code review. Question 10 Part 3 "Bonus Program" ISTQB ISTQB ATTA PDF https://www.certification-exam.com/ During code reviews, it is the author’s responsibility... 1 credit [ Options: A. to address all major and minor defects as stated in the defect log B. to fix all major and minor defects as stated in the defect log C. to take action on only improvement suggestions from the defect log D. to correct source documents that have major defects Answer: A Explanation: The correct answer is A: to address all major and minor defects as stated in the defect log. In a code review, the author is responsible for reviewing the defects identified by the reviewers and taking appropriate action on them. This means the author must address both major and minor defects recorded in the defect log. “Address” is the best wording because it means the author must consider each defect and decide how to resolve it, which may include fixing it, clarifying it, or otherwise handling it appropriately. Why A is correct: - The author must respond to all defects documented during the review. - This includes both major and minor issues. - “Address” is a broader and more accurate term than simply “fix,” because not every defect is necessarily corrected in the source immediately; some may be clarified, deferred, or handled in another way depending on the process. Why the other options are wrong: - B. to fix all major and minor defects as stated in the defect log - Too absolute. Not all defects must necessarily be “fixed” in the literal sense; some may require explanation or alternative resolution. - C. to take action on only improvement suggestions from the defect log - Incorrect because the author must address all defects, not only suggestions for improvement. - D. to correct source documents that have major defects - Incorrect because it ignores minor defects and is too narrow in scope. In summary: The author’s responsibility during code reviews is to ensure all identified defects, major and minor, are addressed appropriately, which is why A is the best answer. Would you like to see more? Don't miss our ISTQB ATTA PDF file at: https://www.certification-exam.com/en/pdf/istqb-pdf/atta-pdf/ ISTQB ISTQB ATTA PDF https://www.certification-exam.com/