ISTQB Updated CTAL-TTA Exam Questions and Answers by diya

Analyzing the given pseudocode for potential anomalies in data flow:

Declare C, F, Z Decimal Set Z = 32 Read F Set C = (F-Z) * 5/9 Free C, F, Z Print F

The potential anomaly is with variable F. It is used after being freed, which typically indicates an error in managing the variable's lifecycle within the code.

• Explanation: Freeing a variable typically indicates that it is no longer available for use, but F is used after this operation, which could result in undefined behavior or errors.

Cyclomatic complexity is a measure of the number of linearly-independent paths through a program's source code, which is often used as a measure of the complexity of a program. The control flow graph provided represents the logic of a software component and has more than 5 nodes with decision points, indicating that the complexity would exceed the maximum allowed value of 5. The calculation for cyclomatic complexity is V(G) = E - N + 2P, where E is the number of edges, N is the number of nodes, and P is the number of connected components. In this case, the calculated cyclomatic complexity exceeds the allowed threshold, thus a defect should be reported.

The pseudo code provided for the Price program shows a potential for an infinite loop due to the way the 'Del_Charge' variable is being manipulated. The loop is set to continue 'WHILE Del_Charge > 0', and within the loop, 'Del_Charge' is initially set to 5 and then potentially decreased by 2 if 'Sale_Value > 60000'. However, at the end of each loop iteration, 'Del_Charge' is increased by 1. This means that if 'Sale_Value' is not greater than 60000, 'Del_Charge' will not decrease and will instead increment indefinitely, causing an infinite loop. Even if 'Sale_Value' is greater than 60000, the decrement by 2 could be negated by the subsequent increments if the loop runs enough times, potentially leading to an infinite loop situation. There is no guaranteed exit condition once the loop is entered, which is a control flow anomaly.

For an exploratory test session, it is important to consider: a) The user roles specified in the user stories, to ensure testing aligns with user expectations and requirements. b) The level of coverage and efficiency to be achieved, to ensure the session is comprehensive and effective. d) The need for documentation of findings from the session, to ensure insights and issues are captured and communicated effectively.

These factors ensure that the exploratory testing is focused, efficient, and its outcomes are actionable and beneficial to the development process .