Many people believe that video game testing is the easiest job in the world. After all, all you have to do is sit down and play video games for eight hours a day...how hard can it be?
Try it.
My challenge to you is to take one day between now and the end of the month, and try to find as many bugs in this game as possible. Find ways to reproduce those bugs, and report them.
Bug reports go here, or get E-mailed to Sam. Follow this template when submitting bugs for maximum bug damage.
Consider this a way for you to find out if game testing really is the dream job that you think it is.
One request for Sam, though...publish the spec. It's hard enough to test a game with a spec...without one, testing is mostly guesswork...
...but then again, I haven't worked on a game with a spec yet...why start now?
1 comment:
I've been a tech writer in high tech for 12 years, and I've worked closely with QA a lot over the last 7+ years. I've learned a lot more about their pain as an observer. The current group I work with is about as an assertive group as I've seen because they do own bug scrubbing alongside the project lead and project manager. They can and do stop releases and do in fact assert a definition of "quality." But the two other QA groups I've worked with haven't had that kind of ownership though they get the attention when a product goes out buggy.
Try writing a good test case. Now try writing one from a poor product design. Come up with all the hardware and software variations likely for a PC game: OSes, patches, video drivers, etc. On top of that, try testing different levels of player abilities.
Then, when you think you have that sussed, try negative testing. Think of doing all the things that you shouldn't be able to do, extending event to hacking and cheats.
I'm reminded of John Lennon's last interview (with David Frost) when he talked about how fun music was in the beginning but then "it had become a job."
Testing != playing games all day
Post a Comment