BorgDrone 22 points 3 years ago

Apparently with all that QA they still missed massive picture quality problems

path: 0 3046033, hotness: undefined, score: 22, children: 24

CreateProblems 63 points 3 years ago

Hey, I work in QA (not in the video game field though.) However, I can tell you there is a difference between "QA missed" and "deadlines required prioritizing other fixes."

One implies that the employees are bad at their job. Which is almost certainly not the case. I haven't played Starfield (or even clicked through to your link lol) but presumably this is something blatantly obvious. And I'm sure the QA team was frustrated letting a glaring known issue through.

QA finds issues but it's up to development teams to fix them, and strict deadlines will always hamper delivering a flawless product. But deadlines are driven by management and until the industry changes (i.e. don't preorder games) we're going to keep seeing these problems.

But as a QA professional, please don't blame us ✌️

save

path: 0 3046033 3051253, hotness: undefined, score: 63, children: 15

stratoscaster 24 points 3 years ago

As someone who works in software dev, QA is a godsend to developers. Thank you for your sacrifice lol

save

path: 0 3046033 3051253 3052920, hotness: undefined, score: 24, children: 0

reverendsteveii 16 points 3 years ago

This. You don't know what's sitting on a jira somewhere with "won't fix" tagged to it. As an ex-QA who's now a dev, we want to fix everything and we get told what we will and will not be fixing. When you see bugs in the final product that are relatively easy to reproduce, the story there is almost certainly that we found it and then the money told us not to bother with it because they think you'll buy the product anyway.

save

path: 0 3046033 3051253 3051481, hotness: undefined, score: 16, children: 6

_stranger_ 7 points 3 years ago

My favorite interaction ever, as a QA:

me: Our integration testing environment is constantly broken due to bad practices among all the teams that share it. They need to be aware of the contract they expose and how they're changing it before they deploy their code to any shared space.

management: Given the recent complaints about the instability of the QA environment, we've decided to shut it down and eliminate all QA positions.

save

path: 0 3046033 3051253 3051481 3055367, hotness: undefined, score: 7, children: 5

MeatsOfRage 7 points 3 years ago

Hell yea brother. Lazy Dev / Lazy QA talk is shit that's gotta stop. Dev here. No one likes to ship buggy code, it's just gonna come back to bite us. Sometimes all you can do is ship good enough code because there are 20 more Jira tickets coming down the pipe.

The teams behind a single AAA game are often as big or bigger than your average tech startup. It's competing priorities all the way up and down the ladder and devs and QA often have very little influence over this.

save

path: 0 3046033 3051253 3062089, hotness: undefined, score: 7, children: 0

WhyIDie 3 points 3 years ago

save

path: 0 3046033 3051253 3052327, hotness: undefined, score: 3, children: 0

BorgDrone -2 points 3 years ago

It’s blatantly obvious and makes the game look like shit. This should not a low-prio bug, this should be a showstopper.

save

path: 0 3046033 3051253 3051319, hotness: undefined, score: -2, children: 4

bleistift2 1 point 3 years ago

If you’ve got 8 minutes to spare, this video explains why it’s not that easy: Why Do We Ship Buggy Games? - A Look Behind the Scenes - Extra Credits

save

path: 0 3046033 3051253 3051319 3119057, hotness: undefined, score: 1, children: 3

Rules:

Rules: