Static Testing
Static testing is the process of evaluating software work products without executing the software to identify defects and improve quality.
“Testing that does not involve the execution of a test item.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Static Testing?
It includes reviews, inspections, walkthroughs, and static analysis performed on requirements, designs, code, and other artifacts.
No software execution: Work products are examined directly.
Early quality improvement: Defects are found before coding or execution.
Broad scope: Includes both manual reviews and automated analysis.
Real World Example
A regulated product team is preparing a release where Static testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Static 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 Static testing and similar ideas.
The page becomes useful in practice because Static testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Static testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Static testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Static Testing. Test your understanding with topic-specific questions in our Mock Exams.