Specialised track

Black Box Software Testing (BBST)

Kaner, Bach & Pettichord's framework for testing as a rigorous intellectual discipline. Critical thinking, oracles, heuristics — the thinking skills behind great testing.

Most testing frameworks tell you what to do. BBST asks something harder: how do you think? Developed by Cem Kaner, James Bach, and Brett Pettichord, Black Box Software Testing treats testing as a cognitive discipline, not a checklist. It teaches testers to reason about whether software is working correctly without access to source code — using oracles to compare actual results against expectations, and heuristics to guide where to look. This track covers the intellectual foundations and the practical tools that define the BBST approach.

Start with Lesson 1 → Back to Specialised

This track covers

BBST History Testing as Cognition The Oracle Problem SFDIPOT FEW HICCUPPS Heuristics

What BBST is

BBST (Black Box Software Testing) is a testing curriculum and philosophy developed by Cem Kaner, James Bach, and Brett Pettichord. It defines testing as a skilled intellectual activity — evaluating a product by learning about it through exploration, applying heuristics to design tests, and using oracles to judge whether results are acceptable. The “black box” framing means you test from the outside: no source code, just the product and your reasoning.

Who this is for

Testers at any level who want to sharpen their analytical thinking beyond scripted test cases. Particularly valuable for manual testers, exploratory testers, and anyone preparing for senior QA roles. ISTQB Foundation Level or equivalent experience recommended.

The 2 modules

The thinking tools behind great testing

Lesson 1

BBST Foundations

What BBST is and where it came from. The intellectual lineage from Cem Kaner, James Bach, and Brett Pettichord. Why treating testing as a cognitive skill — not a process to follow — produces better testers and better results.

~30 min read · ~60 min with exercises · BBST

Lesson 2

Testing Oracles & Heuristics

The oracle problem: how do you know when software is wrong? Oracle types (explicit, heuristic, statistical), and the SFDIPOT and FEW HICCUPPS mnemonics for systematic test ideation.

~35 min read · ~70 min with exercises · BBST

Why this track

Checklists run out. Thinking doesn’t.

A test script tells you what to check. It cannot tell you what you missed. BBST addresses that gap directly: instead of giving you more scripts, it gives you the mental models to generate your own tests in any situation. That is what separates a tester who can work through an unfamiliar feature from one who is stuck without a test plan.

The oracle problem is a good example of this. Every time you say “that result is wrong,” you are consulting an oracle — some basis for comparison. But where does that oracle come from? Is it a specification? Industry convention? Your own experience of how similar systems behave? BBST makes that reasoning explicit so you can apply it deliberately, defend your findings, and recognise when your oracle might be incomplete.

BBST principles align with the ISTQB's emphasis on experience-based testing and are referenced in the Ministry of Testing community curriculum. This track teaches the underlying concepts so that tooling and technique choices become more informed — not the other way around.

Techniques that complement BBST

Technique