pdftract/tests/test_fingerprint_debug.rs
jedarden 225f96c241 fix(pyo3): correct extract_text_fn call in extract_markdown stub
The extract_markdown stub was calling extract_text instead of
extract_text_fn, causing a compilation error. This fixes the
function name to match the exported function from extract_text.rs.

This completes the extract_text PyO3 entry point implementation,
which was already present in extract_text.rs and lib.rs.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-28 20:28:25 -04:00

17 lines
661 B
Rust

use pdftract_core::document::compute_pdf_fingerprint;
#[test]
fn test_debug_fingerprints() {
let v1_path = std::path::PathBuf::from("tests/fingerprint/fixtures/content_edit_one_glyph/v1.pdf");
let v2_path = std::path::PathBuf::from("tests/fingerprint/fixtures/content_edit_one_glyph/v2.pdf");
let fp1 = compute_pdf_fingerprint(&v1_path).unwrap();
let fp2 = compute_pdf_fingerprint(&v2_path).unwrap();
println!("v1 fingerprint: {}", fp1);
println!("v2 fingerprint: {}", fp2);
println!("Equal: {}", fp1 == fp2);
// This should fail
assert_ne!(fp1, fp2, "Content edits should produce different fingerprints");
}