He loves his quaso but is suspicious of the macarons

I hatched so many Honedge trying to get a shiny… and then when I finally got it it had 31SpAtk IV… and Bottle Caps didn’t exist…

‘Twas a simpler time.
Going to Prism Tower with my Talonflame and five eggs and just wedging a dime under my 3DS’s joystick so I could afk while hatching eggs and occasionally pressing A when I saw my character stop moving in my peripheral.

Anyway, a reminder that you can love and enjoy a game and still recognize the faults with it and want more from it. Now if you’ll excuse me, I’m gonna go have some coffee with my Absol 🥰

Again, this from my experience as a Senior QA on a team with 10 people in a company with under 200 total employees. YMMV on how bug severity is graded across different projects.

“How can falling through the map be a minor bug? Idiot.” Well, it’s minor because it doesn’t happen every single time you walk down that alleyway. Simple as that. A bug can crash the game, but if you can’t get the crash to happen again, it’s minor because it’s a “freak incident”.

This therefore, is a minor bug with (relatively) low to no repro and we cannot write a comprehensive bug ticket to give to the devs. We’re not sure if this is a Level Design problem, a Programming problem, an Environment Art problem, etc.

But let’s say we live in a perfect world where every single one of those 325k instances were documented perfectly. Is there ANY correlation between them? Let’s go through the processes with the highest numbers…
God damn it, I still can’t get this stupid thing to repro 😡

Most of the time if you were to ask someone what they were doing as a bug was found, chances are they’ll just go “🤷 I was running and then I fell through the floor. If QA did their job, this wouldn’t happen.” (Cuts to QA slamming head against desk while trying to repro the bug for 5 hours straight.)

Was it on S1 or S2? Docked? Handheld? Connected to the internet? Digital or physical? Downloading something in the background? Is there ANYTHING we can determine that correlates between these 325k theoretical instances? Have those players been able to get it to happen twice in their game?

20 people vs 6.5 million people. If QA found a bug 1/2500 times of testing among 20 people, theoretically it would happen 325k times once launched. Okay, players see it happening live! Can we determine the repro steps from what we’ve seen?

GF has always preferred staying a “small” dev team, and they have around 200 employees. MAYBE if they have an in-house QA team, it’s 10-20 people. (I’m estimating based on the QA team I work in. YMMV.)

… that need to get fixed that we CAN reproduce, so we need to focus man-power on that. Ship, but if we get more information once we go live, we can reopen the ticket and investigate further.” No amount of budget can account for the amount of eyes needed to find these inconsistently repro’d bugs.

When I saw the video I said “yikes, that’s awful, I wonder what the repro rate on this is?” Because if it happens 1/2500 times and the steps to reproduce aren’t consistent, there are times where production just has to say “we don’t understand why this is happening and there are (x # of) other bugs…

RE: that video of someone playing ZA on their S1 and there’s some LOD issues with the textures on buildings being low res and the NPCs popping into view, but the most concerning issue being falling through the floor of the map.

That is, they decide it wasn’t worth the time to fix until Gamers start complaining and tanking the Steam reviews. But by that point, the Gamers have already pointed their fingers specifically at QA for all of these problems.