The basics · 10 min read

What is beta testing? A plain-English explanation

Alpha, beta and release candidate. Open, closed and internal. What testers are actually asked to do, and the three things beta testing is not.

The definition in one paragraph

Beta testing is the stage where software that is feature-complete but not yet released is given to people outside the development team, so they can use it and report what breaks. It happens after the team has finished building and before the version goes to everyone. Its purpose is to find the problems that only appear in real hands: unusual devices, patchy connections, real payment cards, real impatience.

The word comes from an older release convention, alpha then beta, still used because it is short and everyone understands it. You will also hear “early access”, “preview build” and “test flight”, which mean roughly the same thing at different companies.

Alpha, beta, release candidate

Stage	Who uses it	What it is for
Internal or dev build	The team building it	Does the code run at all. Features half built, crashes expected.
Alpha	Usually staff, sometimes a small invited group	Do the features work as designed. Rough, changing daily, data may be wiped.
Beta	Real users outside the company	Does it survive real usage. Mostly complete; problems are the awkward ones: devices, networks, edge cases, load.
Release candidate	A final check group	Is this the exact build we ship. Any fix here restarts the clock.

In practice the lines blur, especially at small companies where “beta” means “the build we gave the testers this morning”. What matters to a tester is not the label but the expectation: a beta build should be usable for real tasks, and it will still misbehave.

Open, closed and internal testing

These three words describe who is allowed in, and they appear literally in the app stores, so it is worth knowing them.

• Internal testing. A small number of named accounts, often up to a hundred. Used by the team and close collaborators. Invitations are personal and short-lived.
• Closed testing. Anyone approved, up to a set limit, usually in the low thousands. You apply, you are accepted or not, and there is often an NDA. This is where most serious volunteer testing happens.
• Open testing. Anyone who finds the listing. No approval, no limit. Useful for load and device coverage, and the least structured: many testers, thin feedback, little contact with the team.

On iOS, most of this runs through TestFlight, which shows you the build, an expiry date and a feedback button. On Android, the Play Console offers the same internal, closed and open tracks, and you opt in from the store listing or an invitation link.

Why companies do it at all

Because software that works on a developer's phone routinely fails on a stranger's. The gap is not laziness; it is arithmetic. A team can own six devices. Their users own tens of thousands of combinations of hardware, OS version, carrier, locale, accessibility setting and network quality.

Beta testing buys four specific things:

1. Coverage. Real devices in real conditions, including the old ones nobody in the office still has.
2. Behaviour no one predicted. People use apps in orders, speeds and contexts the designers did not imagine, and that is where the interesting defects live.
3. A cheaper fix. A bug found in beta costs a support ticket. The same bug found after release costs refunds, reviews and a reputation.
4. Load and money. Real payments, real traffic, real server behaviour. Some things can only be tested by letting people in.

Note what is missing from that list: marketing. A big public beta is sometimes used as a launch run-up, but the reason the discipline exists is engineering, not buzz.

What testers are asked to do

Across almost every programme, the same five asks appear.

• Install the build and keep it updated. Betas ship new versions frequently, sometimes daily. Testing last week's build helps nobody.
• Use it as intended, then use it strangely. Do the normal thing first, then do the awkward thing: rotate the screen, kill the connection, press back at the wrong moment, try to pay twice.
• Report what breaks, precisely. Steps, environment, expected, actual, evidence. One issue per report.
• Answer surveys and checklists. Programmes assess on a schedule, and a completed questionnaire is part of the deal.
• Retest the fixes. When a new build arrives, confirm which of your issues are gone. This is the single most useful message you can send a team.

Three things beta testing is not

Clearing these up saves a lot of disappointment.

It is not a way to get free apps and games

A beta build usually stops working when the programme ends, and many require an active invitation. Joining to keep something for free is the fastest way to be removed, and studios keep records of who did it.

It is not a design review or a wishlist

Beta testers find defects. Preferences belong in a feedback form, clearly labelled, and are not owed a response. “I want a dark mode” filed as a bug lowers your credibility on the bugs that matter.

It is not, usually, a job

Public betas pay in access, not money. Paid testing exists, but it runs through research platforms, per-issue work and contract QA, which is a different arrangement from installing an app because you like the company.

How to join one, today

If you want to see it for yourself, the fastest legitimate path in about fifteen minutes:

1. Install TestFlight on an iPhone, or open an app's Play Store listing on Android and look for the testing section.
2. Find a studio you already use and look for a beta, preview or testing link on their site, newsletter or community channel.
3. Accept the invite, install the build, and use it for ten minutes as you normally would.
4. Find one thing that is wrong and write it up in the five-field format: title, environment, steps, expected and actual, evidence.
5. Send it, then update the app when the next build appears and check whether it is fixed.

That loop, repeated, is the entire discipline. Everything else in this field is a variation on it.

A short glossary

Term	Meaning
Build	One compiled version of the software, identified by a number.
TestFlight	Apple's system for distributing beta builds of iOS and macOS apps.
Closed track	Google Play testing with an approval step and a tester limit.
Reproduction steps	The numbered actions that make a defect happen again.
Regression	Something that used to work and now does not.
Severity	How badly the defect affects the product.
Priority	How urgently the team intends to fix it; not the same thing as severity.
Crash log	The technical record a device writes when an app fails suddenly.
Device matrix	The list of hardware and OS versions a team tests against.
NDA	A confidentiality agreement; common in closed betas.

You do not need to memorise that list. You need to know enough to write a report another person can act on, which is the only definition of a good tester that holds up.

---

Next: how to become a beta tester, and how to get paid to test apps and games.

Still unclear on where you fit, or whether a particular programme is real? Ask us a question.