Sega Settles Discrimination Suit With Filipino Game Testers 49
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."
Say it ain't so (Score:5, Funny)
Re:Say it ain't so (Score:3, Insightful)
But how many of them can really get into a game to fully critique it? (As opposed to, "Duuuhhh... gamez ar fun, doodz!")
Re:Say it ain't so (Score:2)
These people are testers. They can't really critique the games. Not that SEGA's got anybody else to do that...
Re:Say it ain't so (Score:5, Insightful)
It's hard work, but it's not usually SKILLED work, in the sense that you don't need a lot of special training beforehand. I'm SUPER appreciative of our QA staff, but it's not something that you need a degree for. What you DO need is attention to detail, the ability to do monotonous tasks for hours on end, and a willingness to put up with annoying programmers like me that say that the bug can't be reproduced and that you're on crack for suggesting that it's still in the game.
I wouldn't say that QA is 'disposable'. It especially wouldn't be considered that if people knew what the job was like. It ruins a lot of people's ability to play and enjoy games. It really changes your outlook on life, from what I hear. You notice the flaws in everything, and see where OTHER QA departments have failed.
Re:Say it ain't so (Score:4, Insightful)
I always figured you never actually even try to reproduce 'em and just loaf around on slashdot all day...
Guess I was right
You forgot a very important thing. (Score:4, Insightful)
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
Re:You forgot a very important thing. (Score:4, Interesting)
Hehehe, reminds me of my first project. The lead tester wanted to kill me the night before the final deadline (deadlines come and go, but there's a point where its either done or the suits pull the plug).
It was about 2:30 am and I declared "I've become invincible and I don't know how I did it". Turned out it was the result of another bug I'd found an hour earlier, so they only had to fix the first one to get rid of the 2.
That was an 18 hour day, btw, and we still had to come in the next morning (though I did manage to convince them to let us come in only at around 10...woophee).
And the bug wasn't there the day before. They went ahead and added something the day before the deadlines, the fools.
You do have to deduce all of the interrelating systems in a game and how they may misinteract with eachother.
There's also intuition. I was just discussing that at work earlier this week. One of my testers was doing some collision checks and I saw him go around a room and then out, I told him to go back in and try one wall some more. Turns out there was a way to get stuck there. I knew it just looking at him walk in it, and I'm not sure how I did.
Its something in the way the character moved when he was pushing against the wall, I could tell something wasn't right.
There's another guy in the team who gets that collision intuition too. We had a chat about it as they were doing some more of that tedious collision testing. Our conclusion was that it comes from years of playing. You get a subconsious understanding of the conditions of a bug-free region and a bugged region.
Testing is part science, part artform.
Unfortunatly the biggest part is buisness.
And then, there's the mantra of the programmers: Will Not Fix/Not A Defect
Re:You forgot a very important thing. (Score:5, Interesting)
Usually twitching is the dead giveaway. Even the slightest bit indicates that physics broke down. One of the favorite tricks in the first game I worked on (a basketball game) was to wedge a player firmly between two other players, causing him to vibrate slightly, then pass the ball. It would cannon up into the sky, and wouldn't come down for a dozen seconds or more. Nothing in a modern, well designed engine will cause twitches except problems or problem areas.
Slight hitches are also a sign of trouble. If you slide along a wall, and there is the slightest pause, that usually indicates that something isn't quite aligned, and there is a space that you could theoretically squeeze yourself into.
Remember Designers: The clip plane is your friend!
There is also the small space effect... Any time a player's space transitions from enough to not enough along a sloped line instead of a sharp point, problems will occur. You may have to try and wedge a shoulder in there, or filp forward and backwards rapidly, but be it a lower-than-90 degree corner or a small pipe that creeps too low lengthwise, it will cause problems to somebody.
Then there is the bowl effect, where you have a condition that the player should slide down but only encounters another place where they should slide down in the opposite direction. No designer worth his salt would do this normally, but on 80 hour weeks where the only thing to break up the death march is beer...
The pothole effect is about the same, where you have a hole near to the width of the character's collision box, that theoretically they should fall into but the engine can't quite make up it's mind.
There's the penetration ploy... Where you find something pokey and sharp, try to overlap that slightly in a way while walking away from the wall. Many engines will push you back through (or into) the wall. This was most famously demonstrated by The Secret of Mana, where you could traverse characters (including one blocking your return to your home village) by walking up to them and flipping back and forth. 3D engine examples exist too, though none come to mind immediately.
There are others, but those are just what come to mind right now.
And the bug wasn't there the day before. They went ahead and added something the day before the deadlines, the fools.
Don't you just love it when the Lead Programmer starts a conversation by saying "This shouldn't break anything, but we..."
Re:Say it ain't so (Score:2)
Of course, there's always a need for manual testing, but the better testers learn automation skills and move up in the organization.
Re:Say it ain't so (Score:2)
Re:Say it ain't so (Score:2)
This may be picking nits, but if you use anything other than assembly language then you are trusting your code to automatic generation.
Even assembly is interpreted; you'd have to write in machine language to have no generation involved.
I do understand what you were saying, which is why I mentioned the nits. And I don't work in the game industry, which I woul
Re:Say it ain't so (Score:2)
BTW I got to the top of the lighthouse in GTA3 from a boat. Trick is to jump backwards all the way up. Not a bug but a feature
Disposable Employees (Score:5, Insightful)
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
As Someone who thinks he knows something.. (Score:1, Insightful)
Re:As Someone who thinks he knows something.. (Score:2)
Game testing vs software testing. (Score:4, Interesting)
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.
IAALT (I Am A Lead Tester) (Score:4, Insightful)
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.
Re:IAASPL (I Am A Senior Project Lead) (Score:5, Informative)
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.
Re:HRIASPL (He Really Is A Senior Project Lead) (Score:1, Funny)
His last journal entry starts with "Dear Fucktard Little Children..."
Re:Game testing vs software testing. (Score:3, Insightful)
They don't require a tester to know how to code. Nobody in our office had access to the code we were working with for the majority of the time. Everything was done outside, and then we got revs mailed back to us.
To an extent any gamer can be QA. But not every gamer can be GOOD QA. The problem with this lies in the fact that 1 good QA guy in a leadership position can cover up th
What a shocker! (Score:3, Insightful)
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.
Disposable Folks (Score:2, Informative)
Re:Disposable Folks (Score:1)
Those jobs come with two problems.
First you only get around 20-30 hours of work per week and for a college student taking a year off to make some scratch thats a raw deal. You have to get a second job or maybe a third. Second those jobs when working for only a year give you the usual register, stock or maybe a greeter if its a very la
almost? (Score:2)
Not a career, dumbass (Score:2)
Working as a game tester is just like mopping floors at McDonalds. No brains, very tedious, and you're not exactly contibuting any
Re:Not a career, dumbass (Score:5, Insightful)
It is very tedious, but the guys with no brains are laid off pretty damn fast.
There is a big intelectual step from noticing a flaw to describing the exact reproduction process of that flaw.
disposable (Score:2, Insightful)
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.
Re:disposable (Score:2)
Those Amish testers are the worst! Its allways carriages this, barn raising that...
Re:disposable (Score:2)
"Graphical Error: Woman's ankles exposed."
I mean, if they even get THAT in. Most of the time they're just going on and on about the evils of electricity.
Former Sega Employee (Score:5, Interesting)
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.)
Propeller Arena (Score:1)
How do you become a official game tester? (Score:1)
Re:How do you become a official game tester? (Score:2)
Re:How do you become a official game tester? (Score:1)
Re:How do you become a official game tester? (Score:2)
Re:How do you become a official game tester? (Score:2)
Its not a spare time thing, its a full time job.
You find a game company within commute distance of where you live and you apply for the position.
The best place to apply to would be a game publisher, since they usually are the ones in charge of testing (as opposed to the developpers, who are in charge of making buggy games and then refusing to admit that its full of bugs). You need to know how to work in an office (meaning yo