7 ms·
If you think QA is ever complete, then it is clear you have never worked on a QA team. You can always come up with new ideas on how to break things.
by trothoun 12y ago
If you think QA is ever complete, then it is clear you have never worked on a QA team. You can always come up with new ideas on how to break things.
- lovemenot 12y agoI quite agree that one can always come up with new tests. But the pertinent question is whether in this case Nests's QA would have anticipated, yet not tested for, this particular error condition. I believe that on balance the answer is yes, probably they did. A question which follows then is, assuming I am right, what is a reasonable amount of blame for failing to test prior to release?