86
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Jul 2024
86 points (98.9% liked)
Asklemmy
43885 readers
876 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
Actually, that game breaking bug was caught weeks ago by QA. Unmoving deadlines set by upper management meant that a fix couldn't be made in time for the content schedule.
Also, by the time the game has been released for 1 hour, the players have already racked up more playtime than the full QA team could reasonably achieve throughout several years of development (and for most of that time QA were playing an older version…). So, if your game has a lot of player choice, randomization, simulation, complex systems, chances are the players are seeing things that QA never did. And then the players wonder how QA could miss such an obvious bug.
I've mothballed multiple RCs from finding P0 issues by pure chance. In my experience, 90% of bugs are already caught by QA, 8% were isolated bugs that would realistically never get caught in QA, and 2% just slip through.