The Crystal Ball

[6S.Manu]

Originally Posted by ACE-OF-ACES

Some people define 'beta' as software released with a 'bug' in it.. Which is not only un-reasonable but flat out silly! Because by that definition most if not all software is beta, because most if not all software has bugs in the initial release. With that said not only is CoD excluded from being called beta for that reason, but all software is excluded from being called beta for that reason.

Mhm...

A beta test is a limited release of a product with a goal of finding bugs before the final release. Software testing is often referred to by the terms "alpha" and "beta."

Generally speaking, the alpha test is an internal test to find bugs, and the beta test is an external test. During the alpha phase, the product is opened up to employees of the company and, sometimes, friends and family. During the beta phase, the product is opened up to a limited number of customers.

Sometimes, beta tests are referred to as "open" or "closed". A closed beta test has a limited number of spots open for testing, while an open beta has either an unlimited number of spots (i.e. anyone who wants to can participate) or a very large number of spots in cases where opening it up to everyone is impractical.

Beta is needed to find hidden bugs that developer can't easily find.
For example my RL job is to follow the develpment of an application for an industry:
1- Developing: I write the code.
2- Alpha state: I test the application myself.
3- Beta state: I give the application to a industry's guy. He do his tests.
4- Releasing: If the guy say it's OK then the application is released.

Alpha is different from Beta because the develper usually "think" as a developer. He test the application by his logic. Instead the Beta is used by the real customers and a lot of time the customers are "stupid" (logically speaking).. for example they press a key that they don't have to press until something is inserted; the developer is aware of this logic and misses the bug that is going to be found by the customer.

Then it's a problem about resource: the application has a exception that it's thrown if the number of users is over 30 (for example, related to CloD, the bug appear during a multiplayer mission). How can the developer be aware of that bug during the Alpha state?

A) If a software has some hidden bugs inside it does not mean that it's an Beta. It's a bugged sofware.

B) If the software has A LOT of hidden bugs then it's a Beta.

C) If the software has A LOT of hidden bugs and CLEAR and VISIBLE bugs then it's an Alpha.

To which section does CloD belong?