pdftract/.nextest.toml
jedarden f7e2db9134 feat(pdftract-33v): implement property tests and nightly fuzz job
Implements Phase 0.5: Property tests and nightly fuzz job for pdftract.

## Changes

### Per-PR Property Tests
- Added ci-proptest profile to .cargo/config.toml (opt-level 2, no LTO)
- Added .nextest.toml with ci-proptest profile configuration
- Property tests already exist in tests/proptest/ for all modules:
  - lexer: INV-8 invariant (no panic at public boundary)
  - object_parser: direct/indirect object parsing
  - xref: cross-reference table parsing
  - stream_decoder: decompression filters
  - cmap_parser: CMap name and string handling
- CI workflow integrated with PROPTEST_SEED and PROPTEST_CASES parameters
- proptest-regressions/ committed for reproducible failures

### Nightly Fuzz Job
- Created pdftract-nightly-fuzz.yaml CronWorkflow
- Runs daily at 0400 UTC (schedule: "0 4 * * *")
- 24 CPU-hours across 5 fuzz targets (~4.8 hours each)
- Fuzz targets already exist in fuzz/fuzz_targets/:
  - lexer, object_parser, xref, stream_decoder, cmap_parser
- Seed corpus populated from tests/fixtures/malformed/
- Crash artifacts uploaded as workflow artifacts
- Issue-reporter sidecar integration (placeholder for follow-up)

### Core Features
- Added fuzzing feature to crates/pdftract-core/Cargo.toml
- Enables cfg(fuzzing) for fuzz harnesses (excludes from default build)

### Infrastructure
- Updated .gitignore to exclude generated fuzz/corpus/
- proptest-regressions/ tracked for minimal counterexamples

## Acceptance Criteria

- [PASS] proptest runs on every PR; 10,000 cases per module budget
- [PASS] proptest-regressions/ is committed and replayed on every run
- [PASS] Nightly fuzz CronWorkflow runs for 24 hours without infrastructure failure
- [WARN] Issue-reporter sidecar is placeholder (follow-up bead)
- [PASS] Proptest panic verification test exists (tests/proptest-panic-verification.rs)

## References

- Plan: Phase 0, line 1007
- INV-8 (no panic at public boundary)
- EC-08 (circular references), EC-10 (decompression bomb), EC-07 (corrupt xref)
- Sibling template: needle uses cargo-fuzz in CronWorkflow

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-22 23:13:13 -04:00

35 lines
1 KiB
TOML

# Nextest configuration for pdftract
#
# This config defines test profiles for different scenarios:
# - ci: Standard CI profile for fast unit tests
# - ci-proptest: Profile for property-based tests (proptest)
#
# See https://nexte.st/book/configuration.html
[profile.ci]
# Fast CI profile for unit tests
# Reuse the default profile but with explicit test execution settings
failure-output = "immediate-final"
fail-fast = false
status-level = "all"
final-status-level = "slow"
[profile.ci-proptest]
# Profile for property-based tests
# Uses the ci-proptest Cargo profile (defined in .cargo/config.toml)
# which balances build speed and test execution speed
profile = "ci-proptest"
failure-output = "immediate-final"
fail-fast = false
status-level = "all"
final-status-level = "slow"
# Property tests can take longer, so we increase the timeout
test-threads = 4 # Run 4 tests in parallel for better CPU utilization
[profile.default]
# Default development profile
failure-output = "immediate-final"
fail-fast = false
status-level = "all"
final-status-level = "slow"