Skip to content
← All CTFL glossary terms

Static analysis

Tool-based evaluation of code or other work products without executing them, finding e.g. code smells and security weaknesses.

Syllabus chapters: 3

Sources: ISTQB® Certified Tester Foundation Level syllabus 4.0.1 and the official ISTQB® Glossary. Glossary content © International Software Testing Qualifications Board; source: glossary.istqb.org.

Related terms

Static analysis in a practice question

Question 1

Which statement about the work products that static testing can examine is correct?

  1. Any work product with a formal syntax, since static testing is always performed with a tool
  2. Any work product that can be executed, since its behaviour must be observable
  3. Almost any readable work product — requirements, code, test plans, contracts, models
  4. Work products the team produced itself, since third-party material is out of scope
Show answer
  • Any work product with a formal syntax, since static testing is always performed with a toolA formal syntax is needed only for static analysis; a review requires just readability.
  • Any work product that can be executed, since its behaviour must be observableBeing executable is the precondition for dynamic testing, not for static testing.
  • Correct answer: Almost any readable work product — requirements, code, test plans, contracts, modelsAlmost any readable work product qualifies, whoever produced it.
  • Work products the team produced itself, since third-party material is out of scopeThird-party work products such as contracts are named among the examinable ones.

Almost any work product can be examined using static testing; the examples given include requirement specification documents, source code, test plans, test cases, product backlog items, test charters, project documentation, contracts and models. Any work product that can be read and understood can be the subject of a review; only static analysis needs a structure against which it can be checked.

Syllabus section 3.1.1

Question 2

What does a work product need in order to be examined by static analysis rather than review?

  1. It must be readable and understandable by the reviewers taking part
  2. It must be executable, so that the tool can observe its behaviour
  3. It must be free of legal restrictions on analysing third-party material
  4. It must have a structure against which it can be checked, such as a formal syntax
Show answer
  • It must be readable and understandable by the reviewers taking partBeing readable and understandable is what qualifies a work product for a review.
  • It must be executable, so that the tool can observe its behaviourStatic analysis does not execute the work product; that is dynamic testing.
  • It must be free of legal restrictions on analysing third-party materialLegal restrictions explain one exclusion from static testing, not what analysis needs.
  • Correct answer: It must have a structure against which it can be checked, such as a formal syntaxStatic analysis needs a checkable structure, such as a formal syntax.

Any work product that can be read and understood can be the subject of a review. For static analysis, however, work products need a structure against which they can be checked, for example models, or code or text with a formal syntax.

Syllabus section 3.1.1

Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.