test-coverage

To prevent false confidence in Rust test coverage for citation rendering, use shape-aware fixtures and oracle-verified expected outcomes from independent sources like specs or divergence registers. This ensures tests genuinely exercise intended behavioral paths rather than relying on the code's own output.

Oracle-verified testing stops overfitting by requiring expected outcomes to come from independent sources such as fixtures, oracle output, specs, or explicit contracts, rather than the code's own output. This enforces behavior-contract-first validation and prevents tests from simply mirroring current implementation flaws.

Create shape-aware fixtures by explicitly defining reference field shapes for date variants like year-only or no issued field, and contributor variants like editor-only. This matrix approach ensures your Rust tests cover the exact field-modes required for reliable citation and rendering behavior validation.

The best way to audit test coverage for style rendering and oracle execution is to use provided coverage audit scripts alongside a pre/post checklist workflow. This verifies that added fixtures and updated citation scenarios in citations-expanded.json genuinely satisfy the required behavioral paths.

You need to link citation scenarios to fixtures using citations-expanded.json when implementing features, fixing bugs, or writing Rust tests in citum-core. This linkage ensures your test suite genuinely covers intended citation and rendering behaviors and prevents regression by maintaining scenario coverage.