excel-file-registry

Excel test files for debugging parsing issues are selected by matching the reported bug scenario against the registry's catalog of test cases, which maps specific file names and VPS paths to parser types and expected table counts. This allows you to quickly locate the exact file to reproduce the parsing error.

An Excel test file registry provides a centralized catalog of test files, their VPS paths, and expected outcomes like table and item counts to streamline the testing and debugging of Excel parsing and PDF generation functionalities. It ensures validation scenarios are properly documented and easily accessible.

Yes, you can use the registry to locate test files for specific currency modes like CAD during Excel parsing. The registry details specific testing scenarios including parser types, currency settings, and expected results so you can find files matching your exact parsing configuration.

To verify expected results when testing Excel to PDF conversion, check the registry which provides anticipated output metrics such as table count, total amount, and item counts for each listed test file. You compare your generated PDF output against these documented expectations to confirm accuracy.

Yes, the registry supports testing fallback parser scenarios for Excel files by detailing specific test scenarios including fallback parser modes. It helps developers identify the correct test files and expected outputs to validate how the parsing engine handles fallback operations.