Finally, if any test, whether planned or "ad hoc", fails, well, again, the QA guy can't be blamed for that, can he. Not his code.
The biggest problem I see (and experience) is that blame part. Why is blame being placed at all? The developer isn't good at writing specs. Help them get better! The developer wrote a few bugs. DUH! Just try to do the same thing with no bugs...and good luck to ya!
I don't have a problem with QA identifying defects in my code, just don't approach it with the attitude that I suck at what I do. Cause I don't (most of the time).
Then, of course, there's the fact that some developers create applications that are viewed on different platforms (think web development). There are certain things that, without a significant amount of effort for an insignificant different just isn't worth even talking about. I ran into one of these day, QA submitted the bug, God Bless him, and I have no choice but to relegate it to the black hole that is the "known issues" that will never EVER be dealt with, because it's just more effort than its worth.
Communication is, as always the key. Developers shouldn't disdain QA, and won't, as long as they're not looked at as those sucky humans who can't produce bug-free code. | [reply] |
