test(models): add stable_data determinism tests #107
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!107
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-99-stable-data-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 need confidence that
stable_data()handles basic types deterministically, avoiding issues like order variation in dictionaries or sets that lead to unstable issue fingerprints.What changed
test_stable_data_determinismto test dictionary sorting, set transformation, and list/tuple stabilization.Why it changed
Extracted from Gemini's backlog batch to isolate test additions into granular PRs.
Files touched
tests/test_models.pyRelevant context
Closes #99.
Runtime evidence
pytest tests/test_models.pypasses successfully.Known constraints
None.
Explicit out-of-scope
Other models changes.
Requested decision
Approve and merge.
Merge blockers
CI/CD test failures.
approve_merge.
Reviewed as a narrow test-only PR. It adds coverage for model/stable-data 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.