Repository navigation
testing hooks: evaluate PostToolUse bashEditDiff to cover test files written through Bash #5608
Description
Activity
- added 5 commits that reference this issue
on Sep 30, 2026 Commit 14457ae on origin/main (PR #5621, merged 2026-09-30) meets both acceptance criteria.
- Probe row:
docs/specs/tautological-tests/probes.mdhas the section "bashEditDiff (Claude Code 2.1.285, WSL2, 2026-09-30)". It records the field location (tool_response.bashEditDiff), a table of which modes and settings populate it, whether untracked new files appear (they do), and its shape (changedFiles, files, moreFiles). - Scanning:
plugins/testing/hooks/hooks.jsonhas a PostToolUse row with matcher Bash that runshooks/test-scan-bash.sh(up to 4 changed test files per call, each throughtest-scan.sh).plugins/testing/README.mddocuments the precondition (bashEditDiffEnabled) and the cost. A liveclaude -prun in probes.md shows the hook flagging a zero-assertion test written through acatheredoc.
The issue's Scope also asks for a Windows Git Bash probe, but that is not an acceptance criterion. The README records it as a known limit ("Windows Git Bash is not probed"), and running it needs a Windows host (operator-only), so it can be a separate follow-up.
No open PR addresses #5608 (#5603 only lists it as related) and no duplicate was found. The issue has no comments and only the needs-triage label (no needs-decision or needs-human).
- Probe row:
- added a commit that references this issue
on Oct 1, 2026
Problem
The testing plugin's opt-in
test-scanandtest-weakenhooks see test files written through the Write and Edit tools only. A test file an agent writes or edits through Bash (cat > foo.test.ts,sed -i, a generator script) is never scanned. The Release 2 judge plan and the Release 2b mutation-scope plan (#5603) both deferred closing this gap, so it has no owner.Candidate mechanism
PostToolUse
bashEditDiff(beta since Claude Code 2.1.269) lists the Git-tracked files a Bash call changed. Per code.claude.com/docs/en/hooks (fetched 2026-09-30) it is best effort and in public beta; it is recorded in every permission mode only whenbashEditDiffEnabledis set, otherwise only in auto and bypassPermissions modes.Scope
bashEditDiffon the installed version: which modes populate it, whether new untracked files appear, and its shape on Linux and Windows Git Bash.Acceptance
bashEditDiff's behavior on the installed version.Related: #5603 (Release 2b plan, DT10), #5605 (Release 2 judge).
🤖 Generated with Claude Code