Just me ranting here...
It bothers me when talking to other developers and they say things like "I didn't check [the feature]. That's why we have a QA department!". No, that's wrong. It's the developers responsibility to test and ensure that every way they can think of using the software is working well. QA is just a fresh set of eyes to go through the app in a way that the developer hadn't thought of before.
That's why developers have unit tests: so they can regression test the whole app quickly. If it's the developers responsibility to completely regression test the app every day or so, of course they are going to use unit tests. It's impossible to do so otherwise.
If you have a bug opened against you once: no worries, everyone misses something. If it's opened twice: you either didn't write the tests, run them, or the tests are wrong. And if the bug is opened more than that, well, there is no excuse for that.
If you cannot be responsible for the quality of your work, you should move to a role that doesn't require such standards.
Damn QA, they log at least 12 bugs a day against my code. They will hire anyone for that kind of job. They really need to lighten up a little. Maybe even rent Y rated movie.
ReplyDeleteI can't actually tell if you are joking or not...
ReplyDeleteThat's another good reason to have the developers do as much QA themselves though: bugs will mostly be "as designed" or require better documenting how the app "should work".
I think that although developers are partially responsible for the quality of their code, the testing department is there for a reason. If your job is to program something, then it should work, and if not, you should have to fix it. If you have te same bug opened against you multiple times, and you don't fix the problem over and over again, there is a problem. If it's the developer's job to write unit tests, and make sure it passes the tests, then what is the testing team for? They will have to write their own tests, and make sure it passes those. It seems like work would be getting done twice over.
ReplyDeleteI was just messing with you, so don't take my comment seriously.
ReplyDeleteThe testing department is there to find new paths through the app. To test the app in a way that developer had not thought of. I think that the QA dept. should be writing *functional* tests, not unit tests. If they can automate those functional tests, all the power to them.
ReplyDeleteIf the developer has to make sure things work correctly, it makes sense for them to validate it before it goes to QA. The more layers of people an issue goes through the more it costs. The cheapest place to verify that an app is working correctly is in dev.
Jim knows what's up. End of Story...
ReplyDelete