Racha

• Feb 9th, 2006

 

By applying Regression Testing on the modified build.It means by retesting the failed test, & relatively passed tests on the modified build.

Rohan

• Feb 13th, 2006

 

Successful Retesting the defect will ensure you that the defect is fixed and after doing successful regression for the related failed/on which defect was raised in next passes/phase will enusre that the defect is fixed.

nitesh484

 Profile Answers by nitesh484 

• Feb 15th, 2006

 

In quality world you can't say Bug is 100 % fix or 50 % fix . If Bug is fixed than in new verssion we do regression testing to make sure that Bug fix doesn't have any impact on old functionality.

sis

• Feb 15th, 2006

 

How would you say that a bug is 100 % fixed ???

navinm

 Profile Answers by navinm 

• Mar 1st, 2006

 

We can never say that ant testing process is completed coz it is the part of quality, it it is continous monitoring and improving process. We can decide the % of  testing performed on application,  on the behalf of risk analysis.

Pavan

Chary

• Mar 2nd, 2006

 

After fixed the bug, regresion test was done in all aspect on all related modules of the previous bug. If it is ok then we can say that the bug is 100% fixed

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Mar 16th, 2006

 

Hi frends

yes all of our frends are saying is true, we can't say the testing process is ended but we can somewhat said the bug is fixed

After fixing the bug we r going to conduct regression testing on it. afrer successful outputs we said it's fixed and finally closed it. mean while we r also tested the total application once where the fixed bug will causes some more bugs. SO in this manner we can said bug is fixed. but the we can't say that the testing is closed.

Regards,

srinivasulu.B

srinivasulub1981@yahoo.co.in

prabin pradhan

 Profile Answers by prabin pradhan 

• Mar 16th, 2006

 

its not possible. because there is no system/project which is 100% bug free.

Ravi Lobo

• Mar 17th, 2006

 

Yes it is true that no application can be 100% free from bugs. One must make sure the defects found, are logged and reported. This is important as through out the SDLC phase these bugs may come and go after each build/release. These logged defects will help the developer in fixing the defects as and when they appear.

sreedhar_katkam

• Mar 18th, 2006

 

Hi Friends

We cant say thart a product is fully tested that is 100 % and we cant say that bug is fixed if bug is fixed here due to the change of the code the bug may appear at other place for the mean at the place it is identified is solved but we have not took the whole application in ti consideration that is why we can say that the bug is 100 % fixed

Sreedhar katkam

Semanticspace Technologies

rkkumar

 Profile Answers by rkkumar 

• Mar 23rd, 2006

 

hii friends,

READ THE QUESTION PROPERLY,

its not " how to make an application 100% bug free" but its "how would u say tht a particular bug is 100% fixed.

as of my knowledge "u can confirm it after regression testing"

surya30

 Profile Answers by surya30 

• Apr 8th, 2006

 

hi

u said right

its a tricky question

v hv to be care full in handling such quetions

thn q

M.Ragothaman

• Apr 11th, 2006

 

After Fixing the bug, Tester job to do regression testing. once it is completed we can say that that bug is fixed...

Regards

Raghu

Vijay Rentala

• Apr 11th, 2006

 

Hi,

When the functionality passes the retest, the bug is fixed. When you speak about 100%. it depends on the scope of the defect like how the fix is effecting the other features, any changes due to which the other bit doesn't work which used to work before, other unknown implications at that point in time.

Any suggestions?

Thanks

V!

krichow

 Profile Answers by krichow 

• Apr 15th, 2006

 

The simple answer is After Regression test

SCHITTOOR

• Apr 24th, 2006

 

Quality world you can't say Bug is 100 % fix or 50 % fix . If Bug is fixed than in new verssion we do regression testing to make sure that Bug fix doesn't have any impact on old functionality.

Thanks

Srinivasulu.chittoor

vinsingh_2002

 Profile Answers by vinsingh_2002 

• May 2nd, 2006

 

If the client says that the bug is fixed, it means that the bug is fixed and it can be closed.

tanya

• May 24th, 2006

 

Well if you r shipping the product to the client  bugged..........he is not going to say it is fixed ever........and u lost any future business with him!

vijayasekar33

 Profile Answers by vijayasekar33 

• Jun 1st, 2006

 

Hi

Please the see the question again. The question is not "When can you say that a product is bug free?". The question is "How would you say that a bug is 100% fixed?"

The correct answer as per my knowledge is what Racha has already said. The answer is "By retesting the failed test  & relatively passed tests on the modified build". But the Tester should be thorough about the related tests in which impact may occur due to bug fixing.

S.Vijayalakshmi.

IBM India Ltd.

Bharath.P

• Jun 1st, 2006

 

HI

we can say The Bug is 100% Fixed after

1.retesting the fix(Means Re executing those steps where we actually got the bug) successfully

2.Total completion of Regression Testing Successfully  if the fix of those bug is not intoducing any new issues then we can say

The Bug Is Fixed 100%

Bharath.P

Wipro Technologies

we re test the

BISWAJIT PANI

• Jun 19th, 2006

 

In Practical it is not possible to Fix 100% bugs in an application

Regards

Biswajit Pani ( 09986183456)

Panibiswajit@yahoo.com

 

krishna prasad

• Aug 3rd, 2006

 

Hi..It is true that we cant say the application is 100% bug free but we can say that a bug is 100% fixed. For this only we do the regression test.Wizcom Technologies

Ramanjit Singh

• Aug 4th, 2006

 

Hi Guys

Do read my perspective about this question

To answert this question one has to understand the 'question' and the concept behind that.

Here the question is related to fixing a particular bug 100% so it has nothing to do with the Product/Project to be 100% bug free.

Concept is:- How the bug is found? When we perform a certain number of steps and found any non-complinace with the SRS or some failure we report a BUG.

After reporting the BUG and its RECTIFICATION we re-preform the steps to verify the occurance of the BUG. If by performing the same steps no error is coming we CLOSE the bug and it is said to be 100% fixed. Simultaneously, we are doing the REGRESSION Testing to check that while recifying the BUG there is no other BUG generated. If the result of the REGRESSION Testing leads to reporting of no more BUG than the BUG in question is saidto be 100% fixed.

Regards

Ramanjit Singh

 

 

kgopalakrishnamraju

• Aug 23rd, 2006

 

If the bug is not replicating again in future builds or version's then we can say that the bug is 100% fixed

preethi.gollamandala

 Profile Answers by preethi.gollamandala 

• Sep 9th, 2009

 

If the reported bug is working fine with out any disturbances and there are no side effects from the fixed bug then we can say it is fixed.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 26th, 2009

 

You could say that a bug is 100 percent fixed when all of the following conditions are satisfied:

1) Learn everything that can be known about the fixed functionality and develop tests based on this understanding.

2) Become a mind-reader and know the true intentions of the fixed functionality's requirements.

3) Test every possible input that can be accepted by the fixed functionality and verify that every possible output passes your inspection.

4) Test every path of user work-flow that traverses the fixed functionality and verify that each one passes your inspection.

5) Test every business rule that impacts the fixed functionality and verify that each one passes your inspection.

6) Test everything external to the application that influences the fixed functionality and verify that each one passes your inspection.

Rather than devoting your lifetime to prove that this bug is 100 percent fixed for all conditions, I suggest you spend your time and effort proving that the bug is fixed under the very narrow conditions that occurred when you discovered the bug.