ISTQB Chapter 3 Practice Questions: Static Testing

How this level is examined

The review process activities (planning, initiate review, individual review, issue communication and analysis, fixing and reporting) and the roles (manager, author, moderator, scribe, reviewer, review leader) are examined by description. A question tells you what someone did and asks which role or which activity it was. The moderator and the review leader are distinct, and the scribe's job is to record, not to evaluate - both are common misses.

The four review types form an ordered scale of formality: informal review, walkthrough, technical review, inspection. Questions usually give you a characteristic - whether it is led by the author, whether it uses defined roles, whether metrics are collected, whether it produces documented results - and ask which type it identifies. Learn them as a table of characteristics rather than as four paragraphs.

The chapter's rationale, that static testing finds defects early and therefore cheaply, connects back to chapter 1's cost-of-fix argument and to the value of early stakeholder feedback. Expect at least one question on what static testing can be applied to - which is a much wider range of work products than candidates expect, including contracts, models and test cases themselves.

Worked examples

These 5 come with the answer and the reasoning already shown, so you can see what this kind of question looks like before you start. They are drawn from the questions-and-answers page and are deliberately held out of the drill above, so the drill still tells you something you did not already know.