When Should Beta Testing Occur?
Any thoughts on who when beta testing should occur? Who should decide when it should start? Who should manage the information from the output of this test data?
I seem to have a problem with the way my company is handling beta testing. Any ideas on how to change the beta (marketing) testing mentality?
Re: When Should Beta Testing Occur?
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by bman:
Any thoughts on who when beta testing should occur? Who should decide when it should start? Who should manage the information from the output of this test data?<HR></BLOCKQUOTE>
Are we talking "beta" in the form of internal beta or beta in the "release what we hope is not a smoking crater to the public" sense?
This seems to be a problem at many organizations. In many I have been at, beta testing started when QA assured the organization of a stable build based on the requirement and design specifications that it had received. A dubious measure at best, sometimes, with the documentation I have seen. At the very least beta testing should begin when all of the major feature points of the release have been instantiated and tested.
Past that, though, you get into: should they all work? I would say "yes." The point of the beta is really to say this is probably what we are going to release assuming nobody finds any show stoppers (although then you sometimes get into the debate of what constitutes a beta release and a release candidate; to me, a "beta" is a release candidate).