jedarden 613a574c40 test(bf-18a0w): improve assertion messages in cmap_unmapped_glyphs tests

Enhanced all assertion messages in cmap_unmapped_glyphs.rs to follow a consistent pattern:
- What was expected
- What was found
- Why this matters

Modified tests:
- test_cmap_unmapped_glyph_skip: Added detailed messages for unmapped checks, map validation, and lookups
- test_cmap_multiple_mappings_with_unmapped_check: Enhanced mapping verification messages
- test_cmap_range_mapping_with_unmapped_awareness: Improved range expansion and boundary check messages

All 7 tests pass successfully. Assertion messages now provide maximally helpful diagnostics when failures occur.

Verification: notes/bf-18a0w.md

2026-07-06 18:43:34 -04:00

1.5 KiB

Raw Blame History

Verification Note for bf-12to2

Task

Add PdfExtractor import to truncated-flate test module.

Implementation

Status: Already complete - no changes needed

The PdfExtractor import is already present in the test file at line 15:

use pdftract_core::document::{parse_pdf_file, PdfExtractor};

Verification

Compilation Test

cargo test --package pdftract-core test_truncated_flate

Result: ✅ Compilation successful

Exit code: 0 (compilation succeeded)
All tests compiled without errors
No "unresolved import" errors for PdfExtractor

Test Results

4 tests passed
2 tests failed (due to test logic issues with fixture, not import issues)

The test failures are unrelated to the import:

test_truncated_flate_parses_as_pdf - failed because fixture has no pages
test_truncated_flate_partial_content_accessible - failed because fixture has no pages

These failures indicate the test expectations need adjustment for the actual fixture content, but the PdfExtractor import is working correctly.

Files Verified

/home/coding/pdftract/crates/pdftract-core/tests/test_truncated_flate_recovery.rs

Acceptance Criteria Status

✅ PdfExtractor is imported at the top of the test module (line 15)
✅ cargo test --package pdftract-core test_truncated_flate compiles successfully
✅ No "unresolved import" errors

Conclusion

The bead requirements are already met. The PdfExtractor import exists and the code compiles without issues.

1.5 KiB Raw Blame History