Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="Sacrosanct" data-source="post: 7928784" data-attributes="member: 15700">I've never said this was a world ending, or disastrous thing akin to an apocalypse.  Those were all straw man others have associated to me.   I've said not finding this error was unacceptable for anyone remotely doing quality assurance testing.  I said that the core code should not have been impacted (because they said the core code should not have been impacted).  And I said they aren't using alpha or beta testing definitions accurately.  I said my primary issue is what all those things infer (not the actual error itself): that they aren't using quality assurance testing appropriately.  The reason it's my primary concern is because of what it means: that it adds risk of poor code continuing to go out.  Which can give them a poorer reputation.  They are the face of digital D&D, and other companies do similar software applications without these issues, so in a world where they want to keep being the face of digital D&D, they should try to ensure their QA testing is spot on and adheres to industry standards (since industry standards are robustly validated as being effective and accurate).  And if people don't think having good QA testing is important, I shall point them to BAttlefield 4, Daggerfall, Sword Coast Legends (you couldn't even get past he demo dungeon for the first week), Daikatana, Fallout 3 New Vegas, Ultima IX, Battlecruiser 3000 AD, and Fallout 76.  One can easily make the argument that some video game companies that decided to not follow industry standards of quality assurance has resulted in very bad results.</blockquote>

Verification