3 Commits

Include renames

Author	SHA1	Message	Date
swaitsandClaude Opus 5.5	a833229d87	tests: every test dir is removed when its test ends, pass or panic ... Many test helpers removed their temp dir only before the test, or only on pass, so runs left them behind: 117,000 filled /tmp (RAM here) and stopped a mutation run. Each now holds a guard that removes the dir on drop, unwind included; servers started on a test dir hold its guard until they stop. A full cargo test --workspace leaves 0 dirs (859 before). just sweep-test-tmp stays for runs killed mid-test. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T3gXMVt7XJPi6ens1or9Dj	2026-10-17 20:47:44 -06:00
swaitsandClaude Opus 5.5	0cf8fb842f	store: tests for mutation survivors; drop pre-checks the rehearsal covers ... From the first store mutation run (324 caught of 396 viable): - receive_payment and pay_bill repeated the engine's refusals by hand after rehearsing the engine itself, so those checks could never fire (their mutants survived). Removed: the rehearsal is the check. - New hand-computed tests: a disposal's final catch-up after some depreciation was posted (200 of 300, gain 100); a disposal on the purchase date (allowed) or the day before (refused); a retained earnings close with a sweep replays it; a float inside an array is refused; the viewer's journal and head hash. - The concurrency test's reader stops when the writer thread ends, not only when it says it's done, so a mutant that kills the writer fails the test at once instead of spinning to the five-minute timeout. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GWVo7x3UHw5kwCUaWxiejX	2026-10-13 19:32:32 -06:00
swaitsandClaude Opus 5.5	f4381f170c	viewer: no false "database differs" while the books are being written ... New concurrency test: one thread writes entries, drafts and receipts as fast as it can while a Snapshot (the viewer) refreshes in a loop. At every refresh the snapshot's books must balance, never go backward, and never see the writer's database as differing from the journal; at the end it must equal the writer in full. It failed 30 runs in 50: check_disk read the applied position and the tables in separate statements, so a write landing between them made a consistent database look like it "differs", which the viewer shows as a problem in Needs attention. - check_disk reads in one read transaction (one consistent view). - A database that has applied lines the viewer hasn't read yet is now DiskCheck::Ahead ("viewer catching up"), not Behind. - Without the transaction the test fails 14 runs in 20; with it, 50/50. Also: members' equity spec 3b states the exact bound (a member's period income is within two cents of their share, one cent of rounding at each end; the running balance chains exactly), and the spec-blind property checks that bound. docs/testing.md gains the concurrency layer and item 12: each close into members' capital still rounds on its own (pending). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GWVo7x3UHw5kwCUaWxiejX	2026-10-13 18:51:15 -06:00