Repository navigation
test: add WAL durability fault-injection tests for fsync and write failures #210
Description
Source
Extracted from the reliability audit snippet: robust disk fsyncs, checksums, replay logic, and error paths.
Programmatic test scope
Add fault-injection tests around WAL write, flush, sync, and checkpoint deletion paths.
Cases to cover
- WAL append fails before the fact is applied to shared storage.
- WAL sync fails after bytes are written.
- Checkpoint succeeds but WAL deletion fails.
- Checkpoint/main-file sync failure returns an error instead of silently proceeding.
- Error paths do not leave transaction locks or thread-local write state stuck.
Acceptance criteria
- Use a test backend or filesystem setup that deterministically injects failures.
- Assertions verify database state after the failure and after reopen.
- Tests prove no acknowledged commit is lost and no failed commit is visible.
Activity
chore(wave3): foundation — FaultInjectingBackend, fuzz/ crate, propte…
Merge pull request #257 from project-minigraf/wave3/pr2-wal