56 réponses à ce sujet

[Rokayt]

Yajuu Omoi wrote...

DullahansXMark wrote...

Immortal Strife wrote...

Rokayt wrote...

DullahansXMark wrote...

Immortal Strife wrote...
I have been a gamer for more than 20 years I have not seen anything quite like this.

You never played LoZ: Ocarina of Time, have you?

Ben Drowned, Ya know'

I played the first N64 Zelda, in that the same game?

That's the one. You kinda have to hunt for most of them, but they are BAD.

Small example: find a way to lose your sword, and for some random reason you can now use any weapon while on your horse, instead of just the bow. And that's not even all that you can do swordless.

You think LoZ: OoT was bad?
Try Legend of Zelda: A Link To The Past. and I'm not even talking the original, the handheld verson for GameBoy...

Beating a link to the past in 30 minutes isn't too hard with glitches.

Or without getting the sword... Etc.

[Outlawstar15a2]

I'm curious how does being a game tester affect your ability to play and enjoy games at home? I used to do alot of cooking at my previous job and it has left me with a permanent desire not to cook even though I have all the stuff necessary and the skills to do so.

Modifié par Outlawstar15a2, 25 août 2012 - 07:17 .

[Rokayt]

Outlawstar15a2 wrote...

I'm curious how does being a game tester affect your ability to play and enjoy games at home? I used to do alot of cooking at my previous job and it has left me with a permanent desire not to cook even though I have all the stuff necessary and the skills to do so.

Wouldn't that depend on your experience with the job?

[Doctor Schrae]

My most profound apologies to all following this thread. It took forever for me to make it home, traffic was awful, and once I got home I barely made it through two matches before passing out.

The impact testing has on my gaming life at home has been subtle, and at times unnoticeable. But the impact is still there. Its a sort of helpless feeling after you get used to helping things get fixed. The QA tester's job is to find and report issues through guided testing, and sometimes through adhoc testing, which is just choosing a course of action on your own and testing in that manner. So coming across an issue at home leads to my regular course of getting things fixed not falling through. I can't bring this issue up beyond an email to a developer team, and there is usually no reply. I don't feel as though I help with issues discovered at home.

[Shadohz]

Rokayt wrote...

Doctor Schrae wrote...

Rokayt wrote...
At least you get to replicate game breaking bugs that make people headdesk in their daily life over and over....

Every day. And every day we have to explain to developers why our issues are worth fixing, AND we have to tell them what the desired result is. And even then, they might not fix all the issues. They have a nifty little option in their reports that can mark any issue Known Shippable/ As Designed.

I really hope that the "As Designed" bugs only ever are things which are exploitable for fun.

If something like the "N7 Typhoon=Purgatory"* glitches was marked off as an "As designed" bug......
I would RAAAHHHG. Very badly. (Think the Vorcha.)

* Highlight for explaination:(From what I have cross examined, and co-tested.... Half the mods cause strange glitches that have penalties similar to those that the Inferno likened to the punishments of hell. AP mod makes Typhoons damage multipliers vanish, making it terrible against armor.... The Extended mags somehow reduces damage, making the increase in the number bullets availible pointless....)

Nope. "As designed/per designed" issues means someone is Design didn't fully scope an enhancement or poorly covered an item in design docs, Development failed to properly Unit Test, QA failed to properly test,  or an item that hit the field (production/public) was discovered by an end-user, Support or QA that they have no intentions on fixing. Or the failure was on such a colossal level that the company had to say 'we meant to do it that way' because the issue would've been too costly to fix and too embarassing to acknowledge as a problem. Vista, Windows ME and Windows 98 are examples of operating systems with alot "per-design" issues (think trying to map a network share with UAC enabled as an administrator).

In short, if Project Management or Dev comes back with the 'per design" response QA's get hella p*ssed.

Modifié par Shadohz, 25 août 2012 - 03:10 .

[Aesandil]

Immortal Strife wrote...

Op, have you ever seen a game shipped with more bugs than Mass Effect 3. I have been a gamer for more than 20 years I have not seen anything quite like this. Also, how is it that every time DlC is introduced more bugs get incorporated? Maybe Bioware should hire you.

No, no. That infamous achievement is still claimed by Gothic 3. Except there the community was able/allowed to fix a lot of things. 

[Shadohz]

Some of you guys are giving QA's a bad rep. A QA representative with any significant amount of dev (programming), security, networking, or data modeling is just a few steps away from Engineer. I get paid an engineer's salary (because my experience), but don't have an engineer's title (because it would be a 'threat' to team leaders decision-making). For all intents and purpose, my primary responsibility is certifying the product, but I still have voice in enhancements, development changes and design review.

You can have power and salary as a QA tester. You must have ambition, education and an ego to match. If anything it works in your favor. If something goes wrong, then there is at least two other tiers that will get in trouble before you. You won't be one of the first to be let go in a down-sizing, since companies tend to weed out from mid-management and work its way down. It also gives you the ability to keep your feet in the dirt (talking directly with clients and Support) while affecting change up high.

It's an almost thankless job with almost no visible measure of performance. You only know you're doing a good job when noone is repeatedly calling in about the same problems.

Modifié par Shadohz, 25 août 2012 - 03:31 .