34c6a3719d
Create test fixture directories and integration tests for Phase 7 profile validation exit gate: Invalid profiles (tests/fixtures/profiles/invalid/): - unknown-key.yaml: unrecognized extraction tuning key - bad-combinator.yaml: malformed match combinators (scalar not list) - secret-key.yaml: forbidden api_key (PROFILE_SECRETS_FORBIDDEN) - malformed.yaml: unclosed bracket (YAML syntax error) Valid profiles (tests/fixtures/profiles/valid/): - minimal.yaml: smallest valid profile (name, description, priority only) - invoice-minimal.yaml: simplified invoice with match and extraction Resolution fixtures (tests/fixtures/profiles/resolution/): - custom-invoice.yaml: priority 100 overrides built-in (priority 50) - README.md: documents resolution priority order Integration tests (tests/integration/advanced/profiles.rs): - test_invalid_profiles_rejected: validates all 4 invalid profiles fail - test_valid_profiles_accepted: validates all 2 valid profiles pass - test_profile_resolution_order: tests --profile-dir override behavior - test_invalid_fixture_error_types: validates specific error messages Acceptance criteria: ✓ pdftract profiles validate rejects all 4 invalid files ✓ pdftract profiles validate accepts all 2 valid files ✓ Profile resolution order test passes Closes bf-2ypn2
23 lines
526 B
YAML
23 lines
526 B
YAML
# Profile with unrecognized keys (should fail validation)
|
|
name: unknown_key_test
|
|
description: This profile contains keys not recognized by the schema
|
|
priority: 10
|
|
|
|
match:
|
|
any:
|
|
- text_contains:
|
|
patterns: ["test"]
|
|
|
|
# Invalid: not_a_real_key is not a recognized extraction tuning option
|
|
extraction:
|
|
reading_order: line_dominant
|
|
not_a_real_key: this_value_should_fail
|
|
table_detection: strict_borders
|
|
|
|
fields:
|
|
test_field:
|
|
type: string
|
|
extraction:
|
|
patterns:
|
|
- "(.*)"
|
|
fallback: null
|