Static Analysis
Static analysis is the examination of software artifacts, such as source code, without executing the software to identify defects, vulnerabilities, or quality issues.
“The process of evaluating a component or system without executing it, based on its form, structure, content, or documentation.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Static Analysis?
Static analysis uses automated tools or manual techniques to detect problems early in development before the software is run.
No execution: Code is analyzed without running the application.
Early detection: Identifies defects before dynamic testing.
Automation: Static analysis tools quickly scan large codebases.
Real World Example
A regulated product team is preparing a release where Static analysis appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Static analysis 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 analysis and similar ideas.
The page becomes useful in practice because Static analysis is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Static analysis in the context of ISTQB terminology?
Question 2
A tester needs to explain Static analysis to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Static Analysis. Test your understanding with topic-specific questions in our Mock Exams.