test(analysis): add diff-scope filtering tests #111
No reviewers
Labels
No labels
area:ci
area:docs
area:engineering
area:framework-fp
area:test-coverage
dogfood:fn
dogfood:fp
dogfood:friction
dogfood:tp
phase:b
phase:c
severity:critical
severity:high
severity:low
severity:medium
source:deepseek-v4-pro
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/fallow-py!111
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-96-diff-scope-filtering-tests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Canary Context Pack
Product story
Developers rely on
--sinceto run incremental analyses. To prevent regressions where unrelated files leak into the diff scope, explicit tests are required to ensure only files changed in git are reported.What changed
test_diff_scope_filtering_behaviorto verify git diff-based scope isolation.Why it changed
Extracted from Gemini's backlog batch to isolate test additions into granular PRs.
Files touched
tests/test_analysis_filter.pyRelevant context
Closes #96.
Runtime evidence
pytest tests/test_analysis_filter.pypasses successfully.Known constraints
None.
Explicit out-of-scope
Other analysis testing.
Requested decision
Approve and merge.
Merge blockers
CI/CD test failures.
approve_merge.
Reviewed as a narrow test-only PR. It adds diff-scope filtering coverage without changing runtime code.
Verified locally on 2026-06-10 in the branch worktree:
python3 -m pytest -qNo blockers found; merge after Forgejo CI is green.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.