Better Testing of Patches before Deployment

Better Testing of Patches before Deployment

in Suggestions

Posted by: Void.4205

Void.4205

I have noticed the last few patches have increasingly more bugs; I have seen more bugs with the last few patches then ever before. I suspect the quality of Anets software testing is not high enough before releasing a patch.

A few suggestions:

Learn black box, white-box, and fuzz testing before deploying, quit making players do your testing for you.

In addition, when you find bugs fix them the first time, I have seen you release patch, after patch, after patch. I can understand not finding them all the first time even the second or third time, but any more then that is just poor quality.

Why did not you catch them the first time you patched? I realize a game is an enormous undertaking, but there is much more complicated software that if not properly tested would result in catastrophic failure, so there is really no excuse.

Better Testing of Patches before Deployment

in Suggestions

Posted by: lordkrall.7241

lordkrall.7241

Just because they have found a bug doesn’t mean they can just snap their fingers and fix it.
In most cases bugs takes time to solve. Should they stop fixing the “easy” bugs and wait until all the bugs are fixed until releasing a patch?

Krall Bloodsword – Mesmer
Krall Peterson – Warrior
Piken Square

Better Testing of Patches before Deployment

in Suggestions

Posted by: Void.4205

Void.4205

Easy bugs would be detected in black box, white box and/or fuzz testing.