Do you?
Here is what is not:
1. A build of software that is exempt from complaint and criticism.
2. A build of software that is expected to have critical flaws.
3. A build of software that is supposed to just not work.
1. It is a build of software's there should be "complained and criticized about," to provide feedback to developers about bugs, annoyances, dislikes, etc...
2. It is a build of software, that should not be expected to be free from critical flaws, the hope with a beta, is that the beta tester will FIND any flaws and report them. It however does not mean they should be 'expected,' but you must acknowledge the possibility of those flaws appearing.
3. A build of software, that has the possibility to no work, but should not be "expected to not work." If it does not work in a testers environment, the tester is supposed to report feedback, and try to provide details, to correct that problem before it leaves a beta phase.
Most of all, anytime you run beta software, you should not "expect" it to "run flawlessly."
It seems that there are certain companies, that release software in persistent "beta" status, I won't name any names, but that is confusing for some people. It offers an unrealistic expectation of beta software.
Alpha software, is even less refined, and some might argue that certain "beta" releases should have remained "alpha" at this point.
[doublepost=1565557860][/doublepost]
Do you?
Here is what is not:
1. A build of software that is exempt from complaint and criticism.
2. A build of software that is expected to have critical flaws.
3. A build of software that is supposed to just not work.
1. It is a build of software's there should be "complained and criticized about," to provide feedback to developers about bugs, annoyances, dislikes, etc...
2. It is a build of software, that should not be expected to be free from critical flaws, the hope with a beta, is that the beta tester will FIND any flaws and report them. It however does not mean they should be 'expected,' but you must acknowledge the possibility of those flaws appearing.
3. A build of software, that has the possibility to no work, but should not be "expected to not work." If it does not work in a testers environment, the tester is supposed to report feedback, and try to provide details, to correct that problem before it leaves a beta phase.
Most of all, anytime you run beta software, you should not "expect" it to "run flawlessly."
It seems that there are certain companies, that release software in persistent "beta" status, I won't name any names, but that is confusing for some people. It offers an unrealistic expectation of beta software.
Alpha software, is even less refined, and some might argue that certain "beta" releases should have remained "alpha" at this point.