Exercise 3: Why a Test Is "a Stronger Form" of a Review, Not a Separate Practice — Possible Solution ==================================================================== WHAT CHAPTER 7's REVIEW MATERIAL ESTABLISHED ------------------------------ Per Chapter 7, a review's purpose is confirming that a document is still accurate against current reality, on some defined cadence, rather than being left to decay silently. Chapter 7 also warned that a review can be shallow - "a rubber-stamped date bump with no genuine scrutiny behind it" - which still technically counts as "a review happened" without actually verifying anything. WHAT A TEST ADDS ON TOP OF THAT SAME GOAL ------------------------------ Per this chapter, testing means someone genuinely unfamiliar actually attempts to follow the document, or at minimum performs "a careful, skeptical walkthrough" checking every referenced value against current reality. The underlying goal is identical to a review's own goal - confirming the document is still accurate - but the method is far more rigorous, actually exercising the document rather than simply reading it over. WHY THIS MAKES A TEST A STRONGER VERSION RATHER THAN A DIFFERENT ACTIVITY ------------------------------ A shallow review and a genuine test both sit on the same underlying spectrum - both are attempts to confirm "is this document still accurate" - they just differ in how rigorously that question actually gets checked. A test is what a review looks like when performed with maximum rigor: an unfamiliar person genuinely trying to use the document, rather than a familiar person glancing over it and confirming it still looks right to them. WHY THIS CONNECTS DIRECTLY TO CHAPTER 7's OWN WARNING ------------------------------ Chapter 7 already flagged that a review can fail to catch real problems if performed carelessly. Framing a test as the strongest form of review directly answers that concern - it's specifically designed to avoid the shallow rubber-stamp failure mode, since a genuinely unfamiliar tester can't simply glance at something they already understand and confirm it looks fine; they either successfully use the document or they don't. WHY TREATING THEM AS SEPARATE WOULD BE THE WRONG FRAMING ------------------------------ If testing were framed as an unrelated activity rather than a stronger form of review, an organization could satisfy "we review documents regularly" using only shallow reviews and never actually perform a real test - missing the entire point Chapter 7 and this chapter together are building toward, that genuine accuracy verification requires rigor, not just recurrence. WHY THIS WORKS AS AN ANSWER ------------------------------ It restates what Chapter 7's review material established, explains what a test adds in terms of rigor toward the identical underlying goal, and explains why treating testing as the strongest form of review - rather than a separate practice - directly addresses Chapter 7's own warning about shallow, rubber-stamped reviews.