gravikumar123

 Profile Answers by gravikumar123 

• Feb 4th, 2007

 

The context leak seems to stem from a bug handling driver_operations. In this particular case, it is a write operation synthesized from a handle_cntl. In the callback for the write, globus_xio_driver_operation_destroy() is called, but the reference count for the context is not decremented because the operation's reference count is not 0 (the outstanding reference is the write callback which hasn't returned yet).

msusmitha

 Profile Answers by msusmitha 

• Feb 7th, 2007

 

in the bugtracking life cycle if any document regarding the bugs is not having the security then that is called as bug leakage.in the bugtracking tool the object repository can be accessed with the authorised persons,if any one getting the results for that url without having the authorisation then that url is called bug leakage.i think u understoodmadhav_sus@yahoo.co.in

somu_komma

 Profile Answers by somu_komma 

• Feb 7th, 2007

 

Bug leakage is nothing but it check the efficiancy of the tester wheather he has capability or not

Kumar Surapaneni

• Feb 15th, 2007

 

The bugs undiscovered in previous stage is called Bug Leakage

Siva

• Mar 14th, 2007

 

In the context of Black Box testing, a bug/defect leakage results when a bug is  detected which should have been detected in earlier builds/versions of the application. 
A defect which exists during testing ,yet,unfound by the tester,whch is eventually found by the tester/end-user is also called defect leakage..

To give a simplest example, assume that you are doing second round of testing and you found a defect which should have been discoverd during the first
round of testing itself. Such defects are termed as "leaked defects''. If the defect is  cosmetic, such as a spelling mistake, it would not cause any impact on the application but if the defect is a critical one relating to functionality of the applicaiton, it will have serious implications on the whole application.

A couple of reasons which causes defect leakage:

1. Incompleteness of testcases (The test case doesnt have the condition related to that functionality).
2. Improper or incomplete understanding of the application.

Can any more points be added?

Thanks,
Siva

tudhayakumar

 Profile Answers by tudhayakumar 

• May 14th, 2008

 

A bug which is not found by tester but found by the customer.
It might be in UAT or during the maintenance phase