nope. can't be true. no bug count = no job.comrade said:I only found 1 bug and Sony is still calling me back to work on titles for the summer.
nope. can't be true. no bug count = no job.comrade said:I only found 1 bug and Sony is still calling me back to work on titles for the summer.
Well I wouldn't lie about finding less bugs and I can show you the emails asking me if I'm available if you'd like? The job was extremely lax.surume said:nope. can't be true. no bug count = no job.
:lol I know your talking about that Collin's College commercial!Eric WK said:And let's make sure we can use the sound effect from level two.
This one? Whooooosh.
Yeah!
Oblivion said:If anyone has any advice, or any crazy stories in their experience in testing, speak now. I want to know what to expect. Though, it probably might not be that different from what I was doing before.
Just curious, what kind of bugs do you mean that aren't worth bothering with?mrpogi23 said:I have some advice to you... RESPECT THE DEVELOPERS PLS. and we'll respect you when writing your bug report...
as a developer myself, when i get some of the bug report to fix things, testers sometimes report the most STUPIDIEST THINGS, make sure find the important ones that would help make it a better game than what you can nitpick on. Also, decribe it as simple as possible... we dont want to read essays....
I was a tester at EA (now in dev somewhere else) and there was definitely a bug quota. Other testers I've known from Activision and other EA's had similar experiences...it's why they hire you...to find bugs.comrade said:Please don't pass what you don't know off as fact.
kassatsu said:I have game tested for a contractor that deals with Microsoft... try playing IHRA Drag Racing and Crash Bandicoot: Crash Team Racing for 8hrs. You Will Want To Kill Yourself.
DeceitDecide said:I'm just saying being a lowly tester sucks for a lot of people, but it's not a dead-end everywhere you go. My two cents.
MikeOfTheLivingDead said:I worked as a game tester for a about a year, then made games for like 9 years. Here's some advice...
Your communication skills are crucial. Use proper grammar, spelling, complete sentences, and describe the issues you encounter thoroughly. Do not submit hand written notes especially if your penmanship it atrocious. Type up your reports.
Document everything you do.
Do not even try to use technical terms unless you are absolutely positive you understand them and know what you are talking about.
Try not offer your opinion on game play or game design, unless the developer or producer solicits it from you. The developer usually has a dozen people who have never written so much as a line of html telling them how to do their job, don't be one of them.
If you have to prioritize your own bugs, think long and hard about the severity of a bug and if the issue is even a bug. Nothing worse to a developer than having to sift through 500 "bugs" trying to determine what actually needs to be fixed first.
Rather than just sitting and playing through a game repeatedly, try to develop a specific method for testing the game.
Even after a bug is closed, test it thoroughly on every subsequent build you get.
Good luck, have fun.
Oblivion said:..
If anyone has any advice, or any crazy stories in their experience in testing, speak now. I want to know what to expect. Though, it probably might not be that different from what I was doing before.
Eddz said:I spend more time talking and reading about games on GAF than playing them these days. Aside from Pokemon Pearl, I haven't sat and properly played a game this year.
Hey, I think I have the same kind of job that you do.DeceitDecide said:Just fyi... the testers that have it tough are the ones that work for the big publishers like EA, THQ, Microsoft, etc. Those are almost always temp positions that simply bounce candidates back and forth once every 5-6 months. There's virtually no room for advancement, and no way out of the cycle for a lot of guys. I work as a product analyst for a developer (granted a developer that's owned by a major publisher), and I can tell you this is a whole different ballgame. I interface with our artists, animators, sound guys, game designers, and programmers on a daily basis. Really my job is more developer support than strictly entering bugs into a database. We'll have the poor saps from our publisher do that hammering when the time comes for our projects. So, anyway, I'm just saying being a lowly tester sucks for a lot of people, but it's not a dead-end everywhere you go. My two cents.
Hmm, for some games most definitely. For the game I'm working on though, I can see myself playing it after it comes out.Alpha_eX said:For your sake, I hope the game you're testing isn't good because you won't get to enjoy it after testing it to death.
Game Testing sounds fun in reality, but it can get really tiring and repetative.
Ark-AMN said:Hmm, for some games most definitely. For the game I'm working on though, I can see myself playing it after it comes out.
:lol I like the cut of your jib, junior.michaeld said:Hurry and tighten the graphics on level 3
![]()
basis said:never mix hobby with work
Ulairi said:Be prepared for having your hobby destroeyd
DeceitDecide said:Far, far worse consequences. No sane person can spend 8 hours a day reading GAF. Beelzebub himself will hop out of your monitor and steal your very essence...
AtomicShroom said:Not true for me. I've been a tester for 3 years now and I still love gaming just as much. Hell I even play some of the games I tested because they're just that good.
Each row of testers, including mine, has a designated "lead," who manages the team and copies down the data: IP addresses, software version, serial numbers. The star of the leads is Theuret, a man of unerring precision and efficiency, clad in a black T-shirt with dates of the VMC WORLD TOUR listed on the back. VMC isn't a band, though; it's our employer, the company Microsoft has hired to check the Xbox 360 upgrade for bugs.
The process is both grueling and, from the evidence, ineffectual. Last week, Microsoft announced that the "failure rate" of its Xbox 360which some Web sites have pegged as high as 30 percentwas "unacceptable." The company said it was extending its warranty on the machine from one to three years and will take a billion-dollar hit to cover the mess.
Countless cords are plugged and unplugged. Every few minutes, someone else yells "Hard lock!" as a Microsoft executive and a few leads come running over to assess the situation.
In each row, the nine othersmyself included, each of us working since 7:30 a.m.have no choice but to sit and silently assess the chaos. A guy sitting next to me fiddles with his controller, feeling, as we all do, a mildly suicidal mixture of boredom and panic, and then sheepishly asks: "Are we going to get to play today?"
Not today, my friend.
Oblivion said:Yep, soon I will be testing on a sequel to a certain series. A certain series that I think GAF likes. However, the game in question and the developer shall remain shrouded in secrecy. Wouldn't want to be blasted by GAF in case this game turns out to suck when it comes around.
Now, as it turns out, I've worked temporarily as a game tester before for another series that GAF also seems to like. However, that was just more of an off and on position. This is the first time I'm going to be doing this full time.
If anyone has any advice, or any crazy stories in their experience in testing, speak now. I want to know what to expect. Though, it probably might not be that different from what I was doing before.
Bugnology said:
you're welcomekaleii said:Interesting read. Thanks for the link.
Wicked Mint said:Worst job of my life. I still refuse to play the game I tested.
Brannon said:So now you know that you have to tell us what you tested, right? It's your destiny.