Slashdot Mirror
Is Bughunting Still A Way Into the Games Industry?
Edge Online is reprinting an article from last month's issue of the British gaming magazine. In the article, Bug Hunt, they look at the role of the modern QA tester. While once a good way to make yourself known to the company's HR staff, it's more and more simply a summer gig between classes for college students. They also discuss the hard working conditions, soul-crushing scheduling, and the public misconception that what a QA tester does involves the word 'play'. From the article: "Anyone with any experience of the QA process will deny the slightest resemblance between testing a game and playing one for pleasure: finding bugs is unmistakably work, and, by common consensus, very dull and repetitive work at that. On top of this, pay is often poor, job security frail, working conditions extreme and recognition hard to come by. So why do it?"
I'd say that there's a better chance to get into the industry if you're a damn good modder, rather than a damn good bug finder.
Counterstrike(HL), Desert Combat(BF42), and Red Orchesta(UT2004) are all examples of this.
I worked for QA at a major US developer for 3 years (2 of which in a Sr. position) and I have to say that this article does not exaggerate, If anything it was being nice.
The hours are just as terrible as they say in the article, but unlike in the article after the seven months of non stop crunch hours there was no month off, maybe a few days to a week, then you either got fired or moved to another project to start it all over. The equipment is always substandard and often broken. The working situations are always way too cramped. We went even given cubicles; we worked in long rows of tables pressed up against each other so close that 2 people could back up their chairs at the same time.
Using QA as a stepping stone or entry point is no longer an option at all, from what I have seen. Many developers have a very negative image of the people in QA. Out of the 100 people they hired to test probably about 20-40 are actually talented testers, and less then half of that have development skills. Because of this there has been a growing thought that if you work in QA you don't have the talent needed for development work. I have seen people get turned down from a development jobs purely because they currently worked in QA. If you want to make games, you're better off working any normal full time job and making demos/designs docs in your spare time.
Now that I am no longer working for that developer I have much more family/free time, am able to work on my own projects again, and make nearly twice as much as I did while I was in QA (I'm now working in education)
My suggestion for everyone who ever thought about moving into QA, Don't.
Several years ago, just before I left my 'proper job' to work in the games industry I was involved in a pretty disastrous software project. The project and companies involved shall remain nameless, but basics of the story will be familiar to alot of people.
We had a small in-house team (9-10 coders) and the business decided to embark on a project which was way outside of the teams' capacity. After several weeks of protesting that the project was too big for us to deliver in anywhere near the drop dead dates we were given management finally relented and brought in a development consultancy to supplement our small internal team. This consultancy (who will also remain nameless) brought with them a small army of mostly incompetent coders and a giant army of business analysts, architects, project managers and other varieties of monkey trained in various levels of sales and management speak. Needless to say the consultancy left the internal team todo most of the coding work and spent alot of time making presentations, sending long e-mails, creating complex charts of various kinds and then left the delayed, feature barren, burning carcass of of the project behind and pocketed alot of cash.
The one thing that the consultancy brought with them that actually helped was a team of sub-contracted QA staff who were located off-site at the consultancy's office, some miles away. I was even younger and stupider then than I am now and at first I complained bitterly about the 2 page bug reports that I began to receive from them on a regular basis. These reports would contain a massive amount of detail for even the most trivial bug, complete (often 100%) repro cases for bugs which were incredibly complex and (IMO at the time) were never going to be found by normal users. The reports often also contained references to specific areas of the functional specs that we had written at the start of each project which our implementation was not entirely adhering to.
Now that I am less young, less stupid and work in the game industry I pine regularly (as my colleagues will no doubt confirm) for those QA people whose bug reports were so clear, complete, accurate and detailed. The bug reports I receive now from game team testers are like drawings on the wall of a cave when compared to the reports described above. They are short, unclear, often completely inaccurate and sometimes the text is not even recognizable as English.
The reason for this massive discrepancy in report quality is glaringly obvious. When I worked at the consultants office for a little while (just prior to leaving that job) I actually sat next to the QA team. The difference between that QA team and all the QA teams I've worked with in games was like night and day. In a word, they were professionals. Most of them were graduates with 5-10 years of work experience, they were obviously well paid (some of them better paid than me I think) and their personal appearance and hygiene put most of the coders to shame. They had analyzed our entire functional spec, without any interaction with the development team and created a complete test plan which they synced up to our development schedule. They had identified a number of complex testing tools which were appropriate for our product, acquired them and were actively using them to find bugs the we could hardly even imagine. They were often able to isolate the causes of problem, when the cause and effect were in totally unrelated parts of the product (functionally speaking).
That's not to say that the game QA teams I've worked with have been all bad, but they're a totally different class of tester than the guys at the consultancy. I suppose that the title of this post is alittle misleading, as I have also worked with the class of tester found in the games industry in other industries, but they are less common and generally in smaller numbers.
Anyway, before I get modded off topic the real point of this post is that I would like to see the kind of testing described above happen more in the industry