Why inspect a test file in an otherwise tiny feature diff?
The judgment behind the action
Review the whole changed surface, including tests and configuration. Ask whether the changes are necessary, whether they preserve invariants, and whether any new dependencies or permissions are justified. A review is an assessment, not proof of execution.
A bounded way to ask
Review this diff against the task criteria. Identify unrelated changes, weakened tests, and unsupported verification claims.
Find an unrelated storage rewrite in a filtering change.
Why inspect a test file in an otherwise tiny feature diff?
Guided practice contributes completion, not independent mastery.
Make the lesson yours.
Your reflection is attached when you submit your decision. Drafts remain in this tab.
Try it somewhere unfamiliar.
Apply this skill to an unfamiliar repository: find an unrelated storage rewrite in a filtering change. Record the evidence you would need.
Choose your next practiceSource checked 2026-09-09 · Documentation profile · Runtime example untestedOfficial reference