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: 7927861" data-attributes="member: 15700">Bad analogy.  Because with the book, you have no idea what's in it.  With alpha, you do know.  Also, beta and alpha aren't the same.  What do I expect?  I expect exactly what you're supposed to expect in an alpha testing phase (and what was reiterated by their own words): several bugs in the areas included in the alpha testing, but no major breaks to core or existing functionality. Yes, they say encounter builder is in BETA.  But that's not really what Beta testing is, to deploy code to the entire user group for an indefinite amount of time (5 months and counting).  That's not <a href="https://www.guru99.com/alpha-beta-testing-demystified.html" target="_blank">Beta</a> (hyperlinked to definition), that's production code deploy and any errors that are found you just call it Beta (which is another indicator that raises questions about what they are doing QA wise when they are misusing terms and mis-defining testing phases, not to mention, users don't typically do alpha testing to begin with, that's usually internal testing, like what I do at my day job).   Beta testing typically only lasts a couple weeks, which is industry standard for any pilot group, whether it be entertainment or finance.  For practical purposes, "beta" and "pilot' mean the same thing.  Additionally, something in Beta is stable.  It works as designed with only an occasional bug here and there to be found because all the core testing was already done previously.  A Beta build and an Alpha build are entirely different, and it's flawed to assume or imply that one should expect similar reliability between the two.So when they deployed the combat tracker and it totally broke the encounter builder, that is a bad thing.  A very bad thing in the QA industry.  New code broke existing code significantly.  We call it a "show stopper", and it's the highest level defect you can have.   It is not expected just because it's an alpha enhancement, nor should any of us expect that to happen. No one is "looking to get bothered by it".  Don't make excuses for bad testing by insulting the motivations of the people calling it out.Also, because this was mentioned earlier, just because something has frequent updates, is no indicator of whether it's in alpha, beta, or full production.   Existing core production code get updates all the time, because software is a never ending cycle of enhancements.</blockquote>

Verification