No, the same isn't true of everybody. They would all have to miss the exact same details and edge cases, was the point. It's the same reason that you have sensor redundancy, you don't have the same sensor measure twice and trust it.
That's exactly what I meant. With inputs from a diversity of people you can pick up the edge cases more easily. Separately everybody will miss some.
> The developer that wrote the code by definition cannot write an appropriate test suite for it
You said that issue could be applicable to everyone:
> The same is true of pretty much everybody - PMs and QA included. Everybody misses details and edge cases.
I pointed out that the issue can't be true of everybody, since everyone other than the original developer would generally avoid it. You then said I repeated what you said. Which is it?
The same is true of pretty much everybody - PMs and QA included. Everybody misses details and edge cases.
It's better to write the test suite in a readable form and get everyone to take a look at it.
Unit tests are almost entirely unsuitable for this purpose most of the time.