[icarus]

Originally Posted by 6S.Manu

Beta is needed to find hidden bugs that the 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?

No brainer: C

That is why this game is going to take a long, long time to fix.