Bugs still present in the software
During testing you have found 9 bugs and they were fixed. But the software still has 27 bugs which are not found. Should the software be released for the end user to use it?
If the bugs are not found then how does anyone know the number of bugs are remaining. Did the y start with 36 bugs and fix 9?
Releasing with bugs matters if it will harm or give the customer a bad impression.
It depends if there are known workarounds that can be published with the software.
Large software companies openly admit to releasing with tens of thousands of defects. The arguement is waiting to fix all of the bugs would be so expensive that the price would be too high.
It would be better if you fix all bugs and then release to the end user,Or else you can even expose it as for usability test and recommend tester to find bugs in it.
The 27 bugs that are 'not found', were those purposely introduced as control to test QA's effectiveness?
Originally Posted by Pushkar Joshi
If just simply reverting the bad code to remove those bugs, that would be ok to release, but would call to question how well the release process and testing process is if that many control bugs are not found. (that would imply QA is only at a 21% effectiveness)