People occasionally ask what skills it takes to be hired in Quality Assurance.
Okay, that’s a damned lie. Most people are only interested in working in QA as a way to get their foot in the door of the games industry.
But more on that in another post.
Regardless of your reasons for working as a tester, there are some important skills that you must develop to provide quality quality assurance. And they aren’t all what one might expect.
First, the big misconception about working in QA: people outside the games industry think it’s just “playing games all day”. This is sort of like describing gardening as “playing in the grass all day”. Sure, it’ll help if you enjoy that, but it’s definitely underselling the work that’s done.
A Quality Assurance tester is given an early build of a game and then told to find ways to break it. When we find problems, ranging from “here’s a typo” to “this wall doesn’t look right” to “doing things in this complex, obscure order makes this other thing act incorrectly”, then we write detailed descriptions of the problem, how we caused it, and how it can be caused again. If we’re really good - and I am - then we include information pertinent to how it may be fixed (debugging info, dump logs, etc).
A brief disclaimer: technically, this is more accurately known as “Quality Control”, with “Quality Assurance” referring to creation of effective production methods. And yet, it’s still generally called “QA” at many studios. I blame the fact that “QA” is a much catchier acronym than “QC,” and now we’re stuck with it. It’s just as well: if we were called “Quality Testing”, then we’d be forever stuck with people calling us “cuties.”
Regardless, it relies on a strange mix of skills. A good QA tester needs:
Gaming Familiarity - You don’t need to be a game virtuoso, but you need to be able to interact with the game all day, every day, for months. You should be able to play at least as well as the average player, just so you can get your work done and explore the game properly. But try not to play too much better than average all the time - otherwise, you won’t be checking the game thoroughly and realistically.
Observation - Not every bug is as obvious as a crash. Sometimes, a bug will go unnoticed by testers for months, just because no one thought to look at the monster from behind, or no one really read the captions of the conversational dialogue all that closely. In a section that every tester had seen, I found a misuse of “loath” instead of “loathe“. It’s probably the most nitpicking of bugs I’ve found, but it’s still a mistake that can be corrected for a better final product. The devil may not be in the details, but the bugs often are.
Clear, Tactful Communication - You need to be able to clearly express exactly what the problem is and how to recreate it, all while maintaining a certain amount of tact. Remember, you’re talking about how you broke something they’ve been working on for months, and people can get testy. Sadly, the downside of the gaming industry’s loose attitude is the occasional risk of unprofessional egos, so know how to tread lightly when critiquing.
Creativity - Anyone can test for the obvious things, but the bigger and more open the game you’re testing, the more you need to be ready to try crazy shit and see if that works. You need to be able to play a game in a hundred different ways, because there are ten million users out there who want to play the game their way, and they will complain if it doesn’t work.
Development Familiarity - The more familiar you are with the fundamentals of the programming, art, and design sides of the particular game you’re working with, the more specific your bug analysis can be, and the quicker your bugs can be fixed. You can’t be patronizing in your analysis, since they sure as hell know their side better than you, but knowing what clues are useful and what’s chaff makes a big difference.
And, of course, none of these skills will help a tester stand out unless they’re paired with the most important QA skill:
Perseverance - You will be working on the same game every hour, every day, every week, for months. Even the most complex and deepest games will become routine to you. You will hear the same dialogue, complete the same missions, and face the same monsters until they invade your dreams. If you can’t find a way to keep yourself interested, fresh, and energetic, your excitement at working in the games industry will burn out and wither after a few short weeks.
And if you burn out because you lack perseverance, all of your other skills will be useless.
But then again, that can be said of most worthwhile tasks in life, can’t it?