3 ms·
> On some level, I'd say any bug is discoverable through testing - if a user can't experience a bug, then it doesn't exist! Agreed, but this is like saying "fo
by the_af 11y ago
> On some level, I'd say any bug is discoverable through testing - if a user can't experience a bug, then it doesn't exist!
Agreed, but this is like saying "for any (relevant) bug B, I can write a test T that finds it". It doesn't mean you will actually write said test or even be aware you should test for B, even though the end user will later experience it and be harmed by it. This is what Dijkstra seems to be saying: that if your tests don't find bugs it doesn't mean your tests are complete. Important bugs almost surely will happen regardless of your tests. That they pass is a good thing, but it shouldn't instill you with disproportionate confidence that your system works as needed.
- NLips 11y agoI agree much with the article; it was the parent comment I was replying to. I disagree with the idea that a tester shouldn't consider hard-to-find bugs, or performance bugs. I disagree somewhat with the idea that a programmer error or coverage issue is an entirely independent issue from other bugs - if there's no possible manifestation, it's not a bug, and if there is a manifestation, then it's possible to find under another 'class' of bug. I fully agree that we won't execute tests to find all possible bugs. But similarly, code review doesn't find all code errors.