Sega Settles Discrimination Suit With Filipino Game Testers
Thanks to GamePro for its story discussing the $600,000 settling of a discrimination suit brought by Sega game testers who charged that "Sega directed [employment agency] Spherion to terminate the employment of 13 Filipino game testers due to their national origin." Complicatedly, it appears: "The move to fire the Filipino employees stemmed from a complaint of a former employee, who alleged in his exit interview that Sega was giving preferential treatment to Filipinos." Interviews with the testers paint a downbeat perspective of the job, with one of the fired employees saying: "I look around and see some friends who are game testers, and I talk to a couple of people who are in the industry, and what I get from other people is that game testers... are almost disposable."
[W]hat I get from other people is that game testers... are almost disposable
Hate to be the one to break this to you, but the general business concensus in almost any industry is that just about anyone is disposable.
Not that I agree with this, but that is the reality, esp. when an economy is not doing overly well.
- Neil Wehneman
My legal education, in nifty podcast format
Let me tell you, Game testers have by no means the best job in the world. You are there to work. Even if you like the game you're playing (you are truly lucky then) you still have to test it. Test it so much that it no longer seems fun. You have to write a good deal, depending on your company (some companies have very nice methods, but good luck). And you still get treated like you're a janitor.
I think part of the question is how game testing differs from software testing, by which software is stress tested and tested for flaws and problems.
Most software testers are not disposable (except maybe those being outsourced to India, but that's a whole different matter) but they are also active in the coding process to correct software glitches, perform specific tests. Are game testers held by the same criteria, ie. able to code and correct problems, or are they merely there to play the game?
I think the idea behind 'disposable testers' is that they are given the job of playing a game, so naturally the assumption is that it's a BS job or that it's a fun job. Having never been in a game environment, I can't say, but it could be that the job is something akin to a Production assistant working for a studio, where there is so much competition that the position is considered disposable and thus those being hired are treated like so much trash.
I gotta say I have no idea what they're talking about. I certainly never experienced that sort of thing!
No really! Game testers are disposable?! Who would have thought?
Now seriously, the only requirement needed to perform the job when getting hired is a love of games and a decent understanding of computers. You pretty much get taught everything you need to know first day. Basically all that entails is how to write up bug reports.
There were two methos we used. Play game til it crashes. Record what caused the crash, and what error appeared if any. Describe if it was a crash to desktop, a hard lock, a system reset. Then try and recreate that same crash to prove it was repeatable.
Method two involved an actual test plan. This was usually in the later stages of development as the game became stable and playable. Then we'd test all the nit-picky items. Check dialogues for spelling/grammar errors, walk over every pixel, make sure you don't walk through trees and the like, then record all those little things.
Any high school kid with a moderate interest in computers can do this job, and it's a fun job for a little while. It can be real tedious at times as you've worked on trying to recreate one crash for 8+ hours.
Anyone who works for 10 bucks an hour is disposable... and you are probably getting less than 10 so change the word "disposable" to "slave-labor" and it more defines the role. Having to work 100 hours a week must suck. And for the testers I know, they complain... yet they never seem to want another job?
Are game testers held by the same criteria, ie. able to code and correct problems, or are they merely there to play the game?
Testers test.
They don't code, they don't "play", they test, that's their job.
And yes, they are treated as disposable people, its a cool job, it beats washing toilets or flipping burgers, but testers are to the gaming industry what goblins are to fantasy settings or infantry to the military. Call it disposable, expendable, whatever. I call it the bottom of the ladder, and when shit happens, it flows down.
Also, its a contract job. There's work mostly in the summer/fall and not much in the winter/spring (the summer rush ends in october for console games and november for PC games, who don't have to awnser to Sony, Nintendo or Microsoft and who can always get a patch later on).
What I've seen is that they hire testers when a project needs testing, and when its done most of 'em get the axe and the good ones are kept or told they'll be called back when there's a new project.
I might be a tad bitter...
Having never been in a game environment
It shows...
I think the idea behind 'disposable testers' is that they are given the job of playing a game, so naturally the assumption is that it's a BS job or that it's a fun job.
Yeah, because doing 40 to 70 hours a week in the same damn levels over and over again, documenting every little problem...that's fun...
Sheesh.
You can't take the sky from me...
"I get from other people is that game testers... are almost disposable." They're not almost, they fully disposable. As one game magazine mentioned, the next career step after game tester is janitor. Unless you're taking game creation classes on the side while working as a game tester during the day, there's really no career path in game testing other than staying where you are.
Working as a game tester is not something you should plan a friggin' career on. Of course you're going to be disposable - the job takes virtually nothing to qualify for and there's plenty of people willing to do it. If you're *really* lucky, you might get a few contacts in the company you can use if you want to get into game development, but I'm thinking that's pretty damn rare.
Working as a game tester is just like mopping floors at McDonalds. No brains, very tedious, and you're not exactly contibuting anything unique to the company.
=Smidge=
is that game testers... are almost disposable.
Might have something to do with the fact that everybody in the history of the world would take a job where they get paid to play video games? Seriously though, I know the pay isn't all that great, but game tester would probably make a great job to work through college.
Mmmm, -funroll-loops
This is my second post ever to /. As you can tell by my nickname, the last post I submitted was about "Propeller Arena," a cancelled Sega game.
In any case, I'd like to toss in my two cents about this whole deal. First of all, the fired employee who threatened a lawsuit in the first place is Steve Peck. I'll say it again, just so everyone knows. Steve Peck. That's the correct spelling.
Steve Peck is well known throughout the industry for his fanatic love of all things Sega. No kidding. He has a Sonic the Hedgehog tattoo. It's on his leg, if I remember right.
Now, I'm not trying to bash the guy, but he's quite an ass to work with. First off, he's by far the loudest mouth in any office I've worked in in the last 10 years. When he wanted someone's attention, he'd scream at the top of his lungs. He'd frequently do things like pass gas in other employees' cubes. While this may be amusing, the putrid ensuing stink wasn't. He'd also do this in front of new employees, thus showing them that it's okay to be a complete ass at work. He'd also incite pointless Mac vs PC arguments when he should have been working. What do you think your employer would do if they knew you were debating as opposed to working?
The main reason he was fired, and John Amirkhan told me this at the time of his firing, was because Peck decided he wasn't rich enough. Peck was falsifying his hours on his time sheets. Naturally, he was caught and fired. Steve, being the jerk he is, decided he couldn't let Sega management seperate him from his precious position as a game tester, so he threatened the lawsuit. In a blatantly knee-jerk reaction, Sega management proceeded to:
- Fire the test department management
- Fire all of Steve's acquaintances
- Fire pretty much everyone who was Fillippino
That was Sega's mistake. But this pretty much all stemmed from some total ass who couldn't tolerate the fact that the company he so adored wasn't going to pay him to sit around the office (or as the case may be, NOT sit around the office.)
I've always wanted to give it a try, I've done limited betas before(Planet-Side, WC3) so I know I'll be working with incomplete work etc. Anyone know who I should contact about having plenty of spare time to test games? Living in the Miami,FL Area I know of any game studios here..
Been doing the QA thing for quite some time. Much longer than I intended actually, but they pay me too much to up and leave now.
Spot on. Though you paint a bit of a bleak picture and I want to polish it off a bit. Yes there is a high turnover rate for testers. Testers are hired generally on a temp basis, and they know full well what they are getting into when they apply. Being the one in a million long-shot cliche here guy to "make it" is rare. This is typical, though we are hiring a little more than we had been lately. Business is good. =)
Who comes in? Kids right out of high school or college looking for a fun gig before starting college or a career. Some guys make the rounds and seem to bounce from publisher to publisher. Then there is always just the random avid gamer who really really really wants to make games but doesn't have any qualifications other than they are good that them. I personally got hooked in out of school. Just applyed on a laugh. Got it, turns out Im good at it, and Im still here 4 years later. Though the whole bust and everything. HA!
Mostly though turnover is high. Some leave because that thing they were waiting for comes through. Others don't work out. And sometimes there is just no work. The best stay, the rest go, sometimes the medium guys get asked back next year.
Good QA is hard. Its not a BS job nor is it a fun job, but its fun-ish. Its fun for me because I actually enjoy the process more than the gaming. In fact I've pretty much been promoted out of actually playing them!
Are you going to come into a publisher, design a sweet game on their time, sell it back to him and become the next Will Wright? Hell no. Be realistic. Enjoy the job, take it serious, try hard, learn the many levels of the job and yes there are opportunities. Many of my good friends are now designers at various developers all over the US. I look at my AIM list and I can contact devs from coast to coast just to bullcrap. Some others are in production here. They all got hired based on their work right here in QA. Others went on to higher positions in other QA departments.
What's this all about? I don't know anymore. Just that yes, turnover is high in QA, but its because so many people want to do it. Not because it sucks or its not worth it. And some of that turnover is to fill a seat of someone who just got their dream job.
Creativity. Your best testers are the ones that can still come up with ludicrous, ridiculous things to try after doing ludicrous, ridiculous things to this piece of software for 10 hours a day the past 8 months. You know, the ones that decide to feed the big monster the meat of undying gratitude and attack them with the pokey fork of infuriating blindness while pausing and saving during the same frame, only to load the game and, without unpausing, cast the instaneous spell of random teleportation on the poor beast.
From an engineering standpoint it doesn't require a lot of "special training," but the same thing could be said about the marketing department. You need a very broad experience base touching on 3d drawing, programming, design, and gameplay. You do have to deduce all of the interrelating systems in a game and how they may misinteract with eachother. The programmer probably thought to put in a special case clause for doing direct damage to a unit in the same tick that they transfer ownership to the damaging player, but did they remember about area damage? They must have implemented pathfinding around obstacles, and regions of potential interacction around obstacles, but did they remember to update completely surrounded regions of potential interaction when obstacles are removed? I had to create a demo level for the programmers for that last one, so that they would understand what was going wrong.
Testers should not be disposable (until the end of the project *sigh*), because good testers will save a lot of valuable programmer and artist time. Now, most publisher's testing departments I have worked with (and in) have been disposable, simply because their job was not to create the best game possible, but to put in the number of hours as stipulated in the contract. But the in-house teams I have worked in (and with) have all been excellent, focused, and above all, valuable. A programmer could say he saw something weird at a particular location, and go do something more important. When he came back, there would be a %100 repro and parameterization that gave them insight into the problem. With a good QA team, bugs can take minutes to fix. With a bad QA team, that same fix might take hours to figure out.
To misquote Tom Lehrer, a testing department is like a sewer: what you get out of it depends upon what you put into it. The attitude that a testing department is not a skilled position will be reflected in the kinds of testers that you hire and ultimately, the kind of work that they perform.
In other words, demand better. Game development teams are in a position to select great QA people because there's just so bloody many of us. Take advantage of that. Put out your feelers long before the position becomes necessary, and select the best of the best. Pay a livable wage, integrate QA into the process, give them direct access to your programmers, and you will have a truly valuable asset in development.
The alternative is to have a QA department with a high churn and a low useful output. Prophesies tend to self-fulfill.
- Chris Canfield
The ______ Agenda
Straying a bit off the topic... and straying a bit into illegality... but this is really interesting: it seems Propeller Arena is really going to be ripped and leaked at last! Check dreamcasthistory.com's message boards... ~_^
Circumcision is child abuse.
He really is a senior project lead.
His last journal entry starts with "Dear Fucktard Little Children..."
Which of your bullcrappy dev friends was involved in the production of Tony Hawk Pro Skater for the Nokia N-Gage?
I happen work for Spherion in the Corp HQ. Didn't here anything about this but I'm gonna go ask a couple people in the legal dept about this on Monday.