Esplodin, on 21 March 2013 - 12:13 PM, said:
Specific changes should have specific test plans associated with them. Any bugfix dealing with LRM damage should have a step where they fire LRMs to make sure the results of the fix are as expected - you know, to test the fix. One volley of LRM would be enough to tell you something was off in the damage from the debug data. QA sucks the big one and is a lot of repetitive stuff, but this one is a big miss.
Now if this bug caused something unexpected in the test chain (Lrms caused a module to no longer function, or caused the firing mech to lose armor for example) then I agree. No test plan can cover that. However, this is not the case.
I'd like to see something like STO has with a production system and a public "redshirt" test server. Those that want to test the goodies early can, and those that want to play can. Win-win. Although I guess live IS redshirt in this MMO.
I suppose my point was that mistakes can and do happen, regardless of how prepared you are. And has been noted even in the testing grounds that we can use vs the live server, variables in a test environment can and do vary from a live deployment. Either way, it sounds like Paul has a write-up for this anyways, and I admit I could be completely off base with my statements. I'm just attempting to offer perspective from a software development standpoint.
Hindsight is always 20/20, especially for those of us not actually doing the work ourselves.