It is becoming a regular trend although it started years ago, to blame the QA department for every game released in a buggy/broken state.
There is a simple rule that is forgotten each time people talk about this topic and that they don't stop to think about: QA's work is to find and reproduce bugs, not to fix them.
Fixing bug is the programmer's work and, even so, the fact that this bugs remain unfixed is not necessarily their fault either. Both QA and coders have their work conditioned (mainly) by two things; Deadlines and Marketing Decissions. Making it short: The more time a game remains in production, the more expensive it becomes and the harder it will be to make it profitable, hence the Deadlines. Right behind this we have Marketing, whose work is to sell the game in a way that makes it profitable (Release it in a particular time frame: one that maximizes the sales or that stays away from potential competitors.
QA and the coders Seldom have any chance to rise word in that regard. And when they do they are rarely listened to. This is something that we are trying to change in the industry but, in the time being, it is not fair how the fingers are always point to precisely the ones that already deal with time constrains when trying to make their jobs meaningful.
A worthy and deeper read about the topic:
http://www.develop-online.net/news/qa-should-have-the-power-to-delay-games/0219651
Cheers!
Log in to comment