69.2k views
3 votes
You are working as a tester on an online banking system. Availability is considered one of the top products (quality) risks for the system. You find a reproducible failure that results in customers losing their connections to the bank Website when transferring funds between common types of accounts and being unable to reconnect for between three and five minutes.

Which of the following would be a good summary for a defect report for this failure, one that captures both the essence of the failure and its impact on stakeholders?
A. Web server logs show error 0x44AB27 when running test 07.005, which is not an expected error message in /tmp filesystem
B. Developers have introduced major availability defect which will seriously upset our customers
C. Performance is slow and reliability flaky under load
D. Typical funds-transfer transaction results in termination of customer session, with a delay in availability when attempting to reconnect

User Billyjoker
by
8.3k points

1 Answer

5 votes

Final answer:

The best defect report summary is "Typical funds-transfer transaction results in termination of customer session, with a delay in availability when attempting to reconnect" as it clearly states the issue and its impact on availability for customers.

Step-by-step explanation:

A good summary for a defect report in the described scenario would be option D: "Typical funds-transfer transaction results in termination of customer session, with a delay in availability when attempting to reconnect." This summary effectively captures the critical issue of the failure, including the impact on stakeholders, which is crucial for prioritizing the defect resolution.

It clearly communicates the problem that occurs during a common user transaction and the consequential issue affecting system availability.

Such a summary enables developers and product managers to understand the severity of the problem and the negative experience it causes for the customers, thereby highlighting the need for a swift response to address the problem.

User Peitek
by
8.8k points