Black-box Test Technique
A black-box test technique designs test cases based on requirements, specifications, or expected behavior without considering the internal code or structure.
“A test technique based on the specification of a component or system.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Black-box Test Technique?
Black-box test techniques focus on what the system should do rather than how it is implemented. They derive test conditions from externally visible behavior.
Requirement-based testing: Test cases are created from functional specifications and business rules.
No code knowledge required: Internal implementation details are not needed to design tests.
Common techniques: Examples include equivalence partitioning, boundary value analysis, and decision table testing.
Real World Example
A regulated product team is preparing a release where Black-box test technique appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Black-box test technique as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Black-box test technique and similar ideas.
The page becomes useful in practice because Black-box test technique is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which source MOST aligns to black‑box design?
Question 2
Which is NOT typical of black‑box techniques?
Test your knowledge with real ISTQB-style questions
You’ve learned Black-box Test Technique. Test your understanding with topic-specific questions in our Mock Exams.