White Box vs Black Box Testing — What's the Difference?

White box testing is designed with knowledge of the internal code structure (like unit tests written by the developer); black box testing evaluates only inpu...

Published October 6, 2026

Black-box testing checks behaviour from the outside without knowing the code; white-box testing uses knowledge of the internal code to design tests that cover its paths. Teams use both.

The concept

Black-box testers use requirements and inputs/outputs: does the login reject a wrong password? No code access needed.

White-box tests (unit tests, branch coverage) aim to exercise every branch, loop and condition in the implementation.

Viewpoint

black box: input ▶ [ ??? ] ▶ output
white box: input ▶ [ if / else / loop visible ] ▶ output

Practical examples

Black-box API test

curl -s -X POST /login -d 'u=a&p=wrong' -w '%{http_code}'   # expect 401

White-box unit test of a branch

test('free shipping over 50', () => {
  expect(shipping(60)).toBe(0)   // takes the if branch
  expect(shipping(10)).toBe(5)   // takes the else branch
})

Coverage report

npx jest --coverage

Common mistakes

  • Believing 100% coverage means no bugs.
  • Only testing happy paths in black-box tests.
  • Writing tests tightly coupled to implementation details.

Key takeaways

  • Black = outside view, white = inside view.
  • Use black for requirements, white for code paths.
  • Combine both.

FAQ

What is grey-box testing?

A mix: partial knowledge of internals.

Which finds more bugs?

Neither alone; they find different kinds.

More General articles