Skip to content
← All CTFL glossary terms

Inspection

The most formal review type, following a defined process with trained roles, rules, and metrics, aimed at finding the maximum number of anomalies.

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

Inspection in a practice question

Question 1

A review is led by the author of the work product, mainly to establish a common understanding and collect feedback. Which review type is this?

  1. Inspection
  2. Walkthrough
  3. Technical review
  4. Informal review
Show answer
  • InspectionAn inspection is the most formal type with trained roles and metrics, not an author-led discussion.
  • Correct answer: WalkthroughA walkthrough is led by the author to build common understanding and gather feedback.
  • Technical reviewA technical review uses technical experts and a facilitator, not primarily the author.
  • Informal reviewAn informal review follows no defined process; this scenario describes a led walkthrough.

A walkthrough is typically led by the author and can serve to establish common understanding, gather feedback, and find anomalies. Technical reviews use technical experts and a facilitator; inspections are the most formal type, following a defined process with trained roles and metrics.

Syllabus section 3.2.4

Question 2

Performing reviews on small chunks is a success factor for reviews. What is the reason for it?

  1. So that reviewers do not lose concentration during the individual review or the review meeting
  2. So that the author can fix the anomalies from one chunk before the next chunk is reviewed
  3. So that the review leader can select a different review type for each chunk
  4. So that metrics can be collected per chunk and fed back into process improvement
Show answer
  • Correct answer: So that reviewers do not lose concentration during the individual review or the review meetingSmall chunks keep reviewers from losing concentration.
  • So that the author can fix the anomalies from one chunk before the next chunk is reviewedFixing anomalies belongs to a later activity and is not the stated reason.
  • So that the review leader can select a different review type for each chunkChoosing a suitable review type is a separate success factor, not this one's reason.
  • So that metrics can be collected per chunk and fed back into process improvementCollecting metrics is named for inspections, not as the reason for small chunks.

Performing reviews on small chunks is named as a success factor so that reviewers do not lose concentration during an individual review and/or the review meeting when one is held. The other options describe real review concepts — fixing anomalies, selecting an appropriate review type, and collecting metrics in inspections — but none of them is the reason the syllabus gives for small chunks.

Syllabus section 3.2.5

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