Skip to Content
1-22-2009 @ 2:22PM
Speaking as someone that tests software for a living, there is always a missed bug. You just have to react to it as quickly as possible.Some of this stuff is frankly untestable in the PTR. Opening arenas on the PTR wouldn't have helped; there's no way that there could be enough traffic on a standard PTR to adequately test that code. Opening an arena specific PTR might have, if you found some way to convince the hard core players that they should go play with stuff that isn't going to get them rating points. Probably they took a sample of teams, reduced them to their applicable characteristics, fed them into a model of the new matching system, and decided they liked the results. Somewhere along the line someone screwed up that process--the model wasn't right, an attribute was misset or discarded, whatever.Life goes on. You suck it up, patch the immediate problem if possible, fix the underlying problem as fast as you can, and improve your testing procedure for next time.Honestly, I am constantly in awe of Blizzard's ability to keep such a complex system running with as few problems as they do. However hard you think it is to do stuff like this, if you haven't done it, you're underestimating it.
1-22-2009 @ 2:46PM
Well said. Thank you.
1-22-2009 @ 3:16PM
Nicley said. I also work in the software testing / codewriting industry and I can attest to the huge amounts of headaches bugs can be. And I don't mean in fixing them, I mean finding them. I have seen system crashing bugs happen only once and never be reproducable, and seemingly minor bugs become a major headache. No software on a scale as large as this can possibly be completely bug free. There are millions of lines of code involved with keeping this game going and i give a big THANK YOU to the devs that take the time to sift through it all and try to make it better for us. From my insiders-type perspective, I am absolutely amazed that Blizz has put this piece of software together for us to entertain ourselves with, and I will happily fork over my $15 a month to keep enjoying it, bugs and all.
1-22-2009 @ 3:41PM
No one's arguing for bug free releases. But not testing what happens when Wintergrasp changes hands is a basic failure. You should test that anyway as a part of the standard acceptance process to make sure the buff changes correctly, NPCs spawn correctly etc. So when something like "Northrend crashes when WG is won" slips through, you really do have to wonder about their process. Some of this can and should be automated too - it's not like everything needs to have an actual person doing it. Write scripts. For somethings you could probably automate high load via scripts.
1-22-2009 @ 3:52PM
yay! people with some sense of scale :DI too have enormous respect for what blizzard does.perhaps the naysayers would be benefited from looking at it this way. when wow released 4 years ago, it was literally unplayable for a good month. every few hours the servers would restart, and you'd loose everything you'd done for the 30 minutes before it restarted.not being able to play around in northrend for a night is small potatoes to anyone who remembers the game being unplayable by ANYONE for days after patches in days gone by.
1-22-2009 @ 4:15PM
"No one's arguing for bug free releases. But not testing what happens when Wintergrasp changes hands is a basic failure."If that's what happened, I agree.On the other hand, if the updated code that registers the change in possession (which would be where I would start looking given the symptoms) works just fine when it has to update 200 users on a PTR, but panics when it has to update 5,000 simultaneous users on a live realm (numbers randomly made up by me), I'd cut them a little slack. The biggest problem in testing is scaling it up to production level scenarios.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.