this post was submitted on 21 Nov 2024
121 points (88.5% liked)
RetroGaming
19602 readers
378 users here now
Vintage gaming community.
Rules:
- Be kind.
- No spam or soliciting for money.
- No racism or other bigotry allowed.
- Obviously nothing illegal.
If you see these please report them.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Meh, debatable. QA finds the bugs, what to do with them is more a development/production call.
But I can compromise: Speedrunning is competitive QA testing. How about that?
If a bug makes the run take longer they don't investigate it.
Actual counterexample, plenty of optimization came from random guys popping up in the community explaining something they found about the code, that was overlooked for years.
More? A huge emphasis is put on mechanically pulling the run off, which is pointless from a QA point of view, now we can maybe make an argument for TAS in that regard.
Nah, I'd say you're mostly making my point. Optimizing getting through the game fast is absolutely part of the skillset, and random people noticing something obvious everybody had been ignoring is bread-and-butter for testers.
I mean, for testers that care and are going hard, which is where the "competitive" part comes in.
I'm glad you've never done QA in a bank, but in jest, sure, there's a surprising amount of overlapping.
Debatable by dudes with ponytails who use the word "fallacy" 200 times a day, not by people with common sense.