What is a good success criteria for a QA team/tool in such a case? Can simple criteria's like number of bugs lead us to a wrong path?
Ask HN: If the QA tools didn't find any bugs, is the tool bad or the code good?
1–2 of 2 posts
Re: Ask HN: If the QA tools didn't find any bugs, is the tool bad or the code good?
#2Any simple criteria is likely to be faulty in one way or another, and likely to be misinterpreted.
You need good, sound, human judgement to know what the real answer is, and that’s hard to come by.