CTAL-TTA Exam Dumps : Certified Tester Advanced Level Technical Test Analyst

To determine the minimum quantity of test cases that will give 100% statement coverage, we need to ensure that each executable statement in the code is executed at least once. Let's analyze the code step by step to identify the necessary paths:

Valid account number and active account:

Crediting money to the account.

Old balance < zero, new balance >= zero (overdraft cleared).

VIP customer: message sent by email.

Valid account number and active account:

Crediting money to the account.

Old balance < zero, new balance < zero (account overdrawn).

Non-VIP customer.

Valid account number and active account:

Crediting money to the account.

Old balance >= zero.

VIP customer: message sent by email.

Valid account number but inactive account:

Set message "A/c inactive".

Send message by email to supervisor.

Invalid account number:

Add to the count of invalid inputs.

Considering these scenarios, we can see that the minimum number of test cases to cover all statements is three:

Path with a valid, active account, old balance < zero, new balance >= zero, and VIP customer.

Path with a valid, active account, old balance >= zero, and non-VIP customer.

Path with an inactive account or invalid account number.

Therefore, the correct answer is D. 3.

The provided pseudo code for the Answer program shows a WHILE loop that will always execute because the condition for the loop to terminate (a >= d) is never met within the loop's body. This results in an infinite loop. Additionally, since the value of 'b' is initialized with 'a + 10' and 'a' starts from a value that is read and then set to 2, 'b' will never be equal to 12. Therefore, the 'THEN' branch of the IF statement, which includes 'print(b)', is unreachable. These are control flow anomalies because they represent logic in the code that will not function as presumably intended.

Fault seeding and fault injection tools are used intentionally to introduce defects into a system or software to test the robustness of the test suite. This method helps in validating the effectiveness of the test processes and configurations by ensuring that the tests are capable of detecting and isolating inserted faults. It is a technique used to measure the quality of testing rather than debugging or performance compliance, which relates directly to the fundamental purpose of enhancing test coverage and the detection capability of the test suite .