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

Analysis:

The significant non-functional defects recorded for the BestForFood system indicate issues that could be mitigated by appropriate non-functional testing strategies:

Portability Testing:

Ensures that the application can operate in different environments without issues. This could have addressed the defect related to the layout and navigation consistency across different websites (Defect A).

Compatibility Testing:

Ensures that the application works well with other systems and environments. This could have helped in preventing the performance issues noticed in the BestForPensions and BestForMortgages websites after the deployment of BestForFood (Defect B).

Explanation of Incorrect Options:

C. The time taken to diagnose, repair and re-test production defects: This is more related to maintainability and operational processes.

D. BestForFood performance impacted by data growth: This is better addressed through performance and scalability testing.

E. Installation time exceeding agreed timescales: This is related to deployment and operational efficiency.

References:

The ISTQB CTAL-TTA syllabus and standard non-functional testing practices emphasize the importance of portability and compatibility testing for ensuring smooth operation across different environments and systems.

Sources:

ISTQB-CTAL-TTA Syllabus

General knowledge on non-functional testing practices.

Reliability testing is the process of checking whether the software consistently performs according to its specifications. For a commercial system with a critical internet-based user interface, ensuring that the application can handle connection failures without abnormal terminations is essential. Reliability testing would include testing the system's ability to recover from failures and continue operating, which directly addresses the risk identified.

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.