Grey-box Testing
Grey-box testing is a testing approach in which the tester has partial knowledge of the system's internal structure while primarily testing from an external perspective.
“A test type that combines elements of black-box testing and white-box testing.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Grey-box Testing?
Grey-box testing combines aspects of black-box and white-box testing, allowing testers to design more effective test cases using limited implementation knowledge.
Partial visibility: Testers know some internal design details.
Balanced approach: Combines functional behavior with structural insight.
Testing benefit: Internal knowledge helps identify high-risk scenarios.
Real World Example
A regulated product team is preparing a release where Grey-box testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Grey-box testing 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 Grey-box testing and similar ideas.
The page becomes useful in practice because Grey-box testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Grey-box testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Grey-box testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Grey-box Testing. Test your understanding with topic-specific questions in our Mock Exams.