Alexander

“Nobody grins more on their first day on the dev team than someone from QA. Contrary to what people believe, QA people don’t sit around playing games all day. Although they’re the first people to see new titles, one can’t describe their day-to-day routine as fun. It takes meticulous effort to write and verify bug reports. Developers fix bugs at their own pace, after which it becomes QA’s responsibility to test and verify whether the proper adjustment has been made. Some bugs are trivial or are duplicates of others; some are fiendishly difficult to solve and take months or even years to address. Other entries aren’t even bugs and are dubbed “working as intended.” When a problem is discovered by QA, it has to be verified by senior QA staff members. Josh Kurtz described nightmarish experiences he had isolating a bug that occurred whenever a player attacked a monster in Diablo II’s expansion. To eliminate the possibility that a weapon was the culprit of the bug, Josh had to attack a dummy monster using every weapon in the game, a process that took hours. Tasks like these might be split among QA people or sometimes they fell to just one unfortunate soul to sort out. After every weapon was checked, Josh reported the results. The programmers or designers would change something, and Josh would then have to retest every weapon and report results again. The developers would change something else, and Josh would need to test everything again to make sure the bug hadn’t reactivated. And again. After doing something like this repetitively for hours, for days, for weeks, and sometimes for months, QA drudgery feels less like being in a computer game company and more like a psychological experiment. These entry-level positions are minimum-wage jobs, but people endure the experience just for a chance at getting a development position, becoming a QA lead, or attaining some other non-developer position. But everyone’s goal is the same: escape from QA.”
― John Staats, The World of Warcraft Diary: A Journal of Computer Game Development

“They even tried to fill the spots internally with candidates from quality assurance (QA), but that proved a fool’s quest because 3D level design skills took years to develop.”
― John Staats, The World of Warcraft Diary: A Journal of Computer Game Development

“Artist and EverQuest veteran Roman Kenney was well-known for being the most creative exploit-finder in the company. When game designers blocked off unplayable zones with killer mobs, Roman figured out ways past them. For instance, he once performed an action that caused his character to dismount from a flying taxi, dropping him from the flightpath into an off-limits, high-level zone below. His hijinks didn’t stop there. After retrieving his corpse (he died from falling damage) in the forbidden area, he found partially implemented vendors who sold weapons that were better than what was available in the newbie zone loot tables. He clicked on the high-level weapons, linking the stats in world-chat, and asked if anyone wanted to buy them. People enthusiastically made offers thinking he had looted them off mobs. He purchased the weapons from the vendor and resold them for a huge profit. The game designers were amused at his ingenuity, even if it sullied the game’s economy, so they quickly removed dismount actions from our flying taxis to prevent further such excursions.”
― John Staats, The World of Warcraft Diary: A Journal of Computer Game Development

“Another marketing myth Blizzard dispelled after Diablo II was released was the danger of missing holiday sales. When Diablo II slipped into the next year, our sales were still as strong as we had predicted for Christmas. After that Blizzard stopped bending over backwards trying to ship before the end of the year.”
― John Staats, The World of Warcraft Diary: A Journal of Computer Game Development