Stop 02 · Manual Testing FundamentalsTopics · 2/11

Black Box vs White Box vs Gray Box Testing

Part of the QA Testing Roadmap

In short

How much you know about the code changes how you test. Sometimes you test like a user who sees nothing inside, sometimes like an engineer with the blueprints.

Black box testing evaluates functionality without knowledge of internal code, white box testing examines internal logic and structure, and gray box combines elements of both — each fits different testing goals.

The purple blob peers into an open pressure cooker lid while another cooker whistles steam on the stove.

Think of it like this

Checking a pressure cooker

Black box: put rice and water in, see if it whistles and cooks. White box: open the lid, check the valve, the gasket, the safety plug. Gray box: you know it should whistle at a certain pressure, so you test that from outside.

Watch it happen

Three views of the same app

How much you see
Black box
Gray box
White box
Inputs, outputs
UI plus DB, APIs
Code paths

1/4Black box: you only use the app's screens or API. Enter data, check results. No code knowledge needed.

The big ideas

What you need to know

Black box = user view

Great for checking requirements. You find what users would find, but can miss hidden code paths.

White box = code view

Unit tests are white box. They aim to cover branches like every if and else in a function.

Gray box = a peek inside

Place an order in the UI, then run a SQL query to confirm the right row was saved.

Save yourself the pain

Common mistakes

Oops

Thinking black box testing is 'easier' and so less valuable.

Do this instead

Black box tests check what users actually experience. Designing good ones takes real skill.

Oops

Assuming QA never needs to look inside.

Do this instead

Peeking at the database, logs or API responses makes your bug reports far more useful.

Your mission

Go gray on a demo app

~25 min

Quick check

You submit a signup form, then run a SQL query to check the password is stored hashed, not as plain text. What kind of testing is this?

Go deeper

  1. 1Give an example test scenario suited to each approach.
  2. 2Learn why most manual QA work is primarily black box testing.
  3. 3Understand white box testing typically requires programming knowledge to examine code paths.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge