Beta Testing
Beta testing releases a near-final version of software to a limited group of real external users before general availability, gathering feedback and surfacing bugs that internal testing missed. It trades control for realism — beta users bring genuine device diversity, usage patterns, and edge cases a QA team can't fully simulate.
A closed beta limits access to an invited group (early adopters, existing customers); an open beta is available to anyone willing to opt in. Both trade some risk (bugs reaching real users) for a kind of coverage internal testing structurally can't provide: genuinely diverse hardware, networks, and behavior.
Beta programs need their own light infrastructure to be worth running: a feedback channel, crash reporting, and a fast triage loop — otherwise the bugs beta users find never make it back to the team in time to matter before general release.
