Static testing
Testing that evaluates work products without executing them, e.g. reviews and static analysis.
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 testing in a practice question
Question 1
Which statement about the work products that static testing can examine is correct?
- Any work product with a formal syntax, since static testing is always performed with a tool
- Any work product that can be executed, since its behaviour must be observable
- Almost any readable work product — requirements, code, test plans, contracts, models
- 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
Which of the following BEST describes the value of static testing?
- It confirms the software behaves correctly in its target environment before release
- It detects defects in the earliest phases of the SDLC, fulfilling the principle of early testing
- It measures quality characteristics that depend on executing the code, such as performance efficiency
- It identifies the failures the software produces, so the underlying defects can be analysed
Show answer
- It confirms the software behaves correctly in its target environment before releaseConfirming behaviour in an environment requires execution, which static testing does not do.
- Correct answer: It detects defects in the earliest phases of the SDLC, fulfilling the principle of early testingDetecting defects in the earliest phases fulfils the principle of early testing.
- It measures quality characteristics that depend on executing the code, such as performance efficiencyCharacteristics that depend on executing the code are measured by dynamic testing.
- It identifies the failures the software produces, so the underlying defects can be analysedCausing failures and analysing back to the defect is how dynamic testing works.
Static testing can detect defects in the earliest phases of the SDLC, fulfilling the principle of early testing, and can identify defects that dynamic testing cannot find at all. The other three options describe dynamic testing: confirming behaviour in the target environment, measuring characteristics that depend on executing code, and working back from failures to the defects behind them.
Syllabus section 3.1.2
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.