4 ms·
No, that's backwards. Sloppy qa was the root cause of this getting to the beta testers, the fact that it was a prank rather than a mistake is irrelevant. Micros
by gweinberg 4y ago
No, that's backwards. Sloppy qa was the root cause of this getting to the beta testers, the fact that it was a prank rather than a mistake is irrelevant. Microsoft was lucky their sloppy qa was reveled by something so innocuous instead of by a genuinely harmful commit.
- UnpossibleJim 4y ago>>If you read the post, you'd see the QA org saw that Easter Egg, took it in the right spirit (like they should), and signed it okay for beta release (mistakenly, I'd presume) followed by everyone else in the bureaucratic chain that might have okay'd it as well.<< As mentioned above, there were a string of failures. Don't just blame QA for finding the bugs that don't get fixed. If it gets signed off, it gets signed off, there are a bunch of departments that can look at the bug database as well. And, in the end, 9/10 of the people who found this people probably loved the fact that Microsoft finally showed a little bit of soul.
- watwut 4y agoSloppy QA does not causes pranks and bugs. And given that this is forum for developers, developers dont get to blame QA for pranks originating in development. Seriously.