test(analysis): add deterministic cycle issue ordering tests #108
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!108
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-98-deterministic-cycles-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
To prevent cycle noise and constant PR changes in findings, the tool must guarantee a deterministic sorting of circular dependency issues. Tests need to explicitly ensure this property across independent analyzer runs on the same codebase.
What changed
test_deterministic_cycle_issue_orderingto verify cycle sorting and fingerprint generation determinism.Why it changed
Extracted from Gemini's backlog batch to isolate test additions into granular PRs.
Files touched
tests/test_analysis.pyRelevant context
Closes #98.
Runtime evidence
pytest tests/test_analysis.pypasses successfully.Known constraints
None.
Explicit out-of-scope
Other analysis testing changes.
Requested decision
Approve and merge.
Merge blockers
CI/CD test failures.
approve_merge.
Reviewed as a narrow test-only PR. It adds characterization coverage for analysis determinism/cycle behavior 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.