Match each objective to the correct test level Objective:
A) Verifying whetherthe functionalandnon-functlonalbehaviorsof the system are as designed andspecified.
B) Verifying whetherthe functionalandnon-functlonalbehaviorsof the interfaces are as designed.
C) Verifying whetherthe functionalandnon-functionalbehaviorsof the components are as designedand specified.
D)Establishing confidence in the quality of the systemas a whole. Test Level:
* 1.Component testing. 2.Integration testing. 3.System testing. 4.Acceptance testing.
Correct Answer:C
The test levels and their objectives can be matched as follows:
✑ Verifying whether the functional and non-functional behaviors of the system are as designed and specified (A3: System testing).
✑ Verifying whether the functional and non-functional behaviors of the interfaces are as designed (B2: Integration testing).
✑ Verifying whether the functional and non-functional behaviors of the components are as designed and specified (C1: Component testing).
✑ Establishing confidence in the quality of the system as a whole (D4: Acceptance testing).
A company wants to reward each of its salespeople with an annual bonus that represents the sum of all the bonuses accumulated for every single sale made by that salesperson. The bonus for a single sale can take on the following four values: 3%, 5%, 7% and 10% (the percentage refers to the amount of the single sale). These values are determined on the basis of the type of customer (classified as "Basic" or "Premium") to which such sale was made, and on the amount of such sale classified into the following three groups G1, G2 and G3:
• [G1]: less than 300 euros
• [G2]: between 300 and 2000 euros
• [G3]: greater than 2000 euros
Which of the following is the minimum number of test cases needed to cover the full decision table associated with this scenario?
Correct Answer:B
The minimum number of test cases needed to cover the full decision table associated with this scenario is 6. This is because the decision table has 4 conditions (type of customer and amount of sale) and 4 actions (bonus percentage). The conditions have 2 possible values each (Basic or Premium, and G1, G2 or G3), so the total number of combinations is 2 x 2 x 2 x 2 = 16. However, not all combinations are valid, as some of them are contradictory or impossible. For example, a sale cannot be both less than 300 euros and greater than 2000 euros at the same time. Therefore, we need to eliminate the invalid combinations and keep only the valid ones. The valid combinations are:
Type of customer Amount of sale Bonus percentage Basic
G1 3%
Basic G2 5%
Basic G3 7%
Premium G1
5%
Premium G2
7%
Premium G3
10%
These 6 combinations cover all the possible values of the conditions and actions, and they are the minimum number of test cases needed to cover the full decision table. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents,
Select the roles required in a formal review:
Correct Answer:A
In a formal review, the roles involved typically include the author, management, facilitator (also known as moderator), review leader, reviewers, and scribe. Each role has specific responsibilities to ensure the effectiveness and efficiency of the review process:
✑ Theauthorcreates and refines the work product being reviewed.
✑ Managementallocates resources and supports the review process.
✑ Thefacilitatormanages the review meeting, ensuring it proceeds smoothly.
✑ Thereview leaderplans the review and ensures it meets its objectives.
✑ Reviewersexamine the work product to identify defects.
✑ Thescriberecords issues raised during the review meeting.
A program is used to control a manufacturing line (turn machines on and off. start and stop conveyer belts, add raw materials to the flow. etc.). Not all actions are possible at all times. For example, there are certain manufacturing stages that cannot be stopped - unless there is an emergency. A tester attempts to evaluate if all such cases (where a specific action is not allowed) are covered by the tests.
Which coverage metric will provide the needed information for this analysis?
Correct Answer:D
Branch coverage is a type of structural coverage metric that measures the percentage of branches or decision outcomes that are executed by the test cases. A branch is a point in the code where the control flow can take two or more alternative paths based on a condition. For example, an if-else statement is a branch that can execute either the if-block or the else-block depending on the evaluation of the condition. Branch coverage ensures that each branch is taken at least once by the test cases, and thus reveals the behavior of the software under different scenarios. Branch coverage is also known as decision coverage or all-edges coverage.
Branch coverage is suitable for testing the cases where a specific action is not allowed, because it can verify that the test cases cover all the possible outcomes of the conditions that determine the action. For example, if the program has a condition that checks if the manufacturing stage can be stopped, then branch coverage can ensure that the test cases cover both the cases where the stage can be stopped and where it cannot be stopped. This way, branch coverage can help identify any missing or incorrect branches that may lead to undesired or unsafe actions.
The other options are not correct because they are not suitable for testing the cases where a specific action is not allowed. Code coverage is a general term that encompasses various types of coverage metrics, such as statement coverage, branch coverage, data flow coverage, etc. Code coverage does not specify which type of coverage metric is used for the analysis. Data flow coverage is a type of structural coverage metric that measures the percentage of data flow paths that are executed by the test cases. A data flow path is a sequence of statements that define, use, or kill a variable. Data flow coverage is useful for testing the correctness and completeness of the data manipulation in the software, but not for testing the conditions that determine the actions. Statement coverage is a type of structural coverage metric that measures the percentage of statements or lines of code that are executed by the test cases. Statement coverage ensures that each statement is executed at least once by the test cases, but it does not reveal the behavior of the software under different scenarios. Statement coverage isa weaker criterion than branch coverage, because it does not account for the branches or decision outcomes in the code. References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54.
Which of the following statements best describes the difference between product risk and project risk in software testing?
Correct Answer:B
Product risk involves the potential issues that can affect the quality and functionality of the software product, such as defects, performance problems, and usability issues. Project risk, on the other hand, relates to the risks that can impact the project's schedule, budget, and resources, such as delays, cost overruns, and resource constraints. Understanding both types of risks is crucial for managing and mitigating potential problems in software projects.
References:ISTQB CTFL Syllabus, Section 5.2.1, "Risk Management in Testing."
Which of the following statements about checklist-based testing is TRUE?
Correct Answer:D
Checklist-based testing is a technique where testers use pre-determined checklists to ensure that important aspects of a work product are evaluated. Over time, these checklists should be reviewed and updated periodically to maintain their effectiveness in detecting defects. As systems evolve, outdated checklists may miss new types of defects, thus diminishing their usefulness. Therefore, statement D is true according to the ISTQB CTFL syllabus.