RE: How would you say that a bug is 100 % fixed ???
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.
RE: How would you say that a bug is 100 % fixed ???
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.
RE: How would you say that a bug is 100 % fixed ???
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.
RE: How would you say that a bug is 100 % fixed ???
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
RE: How would you say that a bug is 100 % fixed ???
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.
RE: How would you say that a bug is 100 % fixed ???
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.
RE: How would you say that a bug is 100 % fixed ???
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
