Almost everyone gets what defines a beta wrong. Just like they get what defines a desert wrong. A desert is defined by annual precipitation, and Antarctica is the world’s largest desert. I’ll let y’all do the research on that.
A beta test is any test conducted by people who did not write the software. It has nothing to do with where in the SDLC (software development life cycle) the software is.
It could be the first few pages of code, or it could be the final code right before it goes to the factory to be mass copied and boxed. It matters not. All that matters is that the people playing it had nothing to do with creating it.
They did do some beta testing, but it was closed and they apparently did it via LAN. That means they used a small number of people and used a local area network. So the networking topology we’re using never got tested, and no part of the game got tested by the numbers of people who would really be using it.
As an aside, alpha testing is what testing is called when people who wrote the software test it it.
Anyway, Halo 3 and Halo Reach had fully open public betas and they released as complete games with all the features working from day one.
We can quibble over the good and bad of having and not having a public beta and get nowhere but here are three facts that cannot be disputed:
Halo 3 had a public beta, everything worked from day 1.
Halo Reach had a public beta, everything worked from day 1.
Halo 4 had no public beta; there is no web based file share, console based file share has very limited functionality and isn’t working as originally intended, no theater mode for campaign or SpOps due to last minute engine changes, skilled based ranking system not in place at release, and the list actually goes on.
Shoulda had a beta