Never miss a great news story!
Get instant notifications from Economic Times
AllowNot now

You can switch off notifications anytime using browser settings.
Stock Analysis, IPO, Mutual Funds, Bonds & More

Definition of 'Zero Bug Bounce'

Definition: Zero Bug Bounce (ZBB) is that point of defect management technique when developers have fixed all the open bugs raised by the QA team and have succeeded in accessing the test teams’ defect discovery rate. The bounce occurs when the QA team again finds some additional bugs in the next QA cycle and the developer team has to do the detection. After the initial bounce, the rate of discovery of bugs decreases gradually further until the application is stable enough to push into production.

Description: This defect management technique is made popular by Microsoft. The Zero bug bounce is tracked in terms of a graph whereby we chart the number of open defects detected at the end of the day.

Some of the important points for ZBB:

• It is not necessary that bounce always happens at Zero.

• The initial bounce is more pronounced at the end of the test execution cycle

• Using the height and length of the ripple effect, in addition to the timing of initial bounce, it can be determined very easily if the application is stable enough to be pushed into production. Zero bug bounce is very helpful in improving the ability to manage and track a test effort. Utilizing the ZBB graph helps to measure and track test progress and thus ensures the timely and accurate delivery of a high-quality application to the production environment.

Other useful Links

Copyright © 2020 Bennett, Coleman & Co. Ltd. All rights reserved. For reprint rights: Times Syndication Service