Those are usually locked away behind command lines and they don’t test with random chance or such. You trigger the things directly. Realistically what probably happened is some engineer wrote the system slightly wrong and no one caught it. Possibly maybe a designer requested the romance to be more prominent and the solution on engineering side was to tweak a value. It’s be surprised if anyone changes hard coded values for QA. It’s not the 90s anymore where qa is the engineering team.
Those are usually locked away behind command lines and they don’t test with random chance or such. You trigger the things directly. Realistically what probably happened is some engineer wrote the system slightly wrong and no one caught it. Possibly maybe a designer requested the romance to be more prominent and the solution on engineering side was to tweak a value. It’s be surprised if anyone changes hard coded values for QA. It’s not the 90s anymore where qa is the engineering team.
Or perhaps the QA team is especially horndog, like some statistical anomaly.
Probably not, but funny to think about.
QA aren’t build engineers. They don’t get to pick what makes it into a build. If anything it’d be sometime in design or engineering. Not QA.