CodeVetter · Repo Unpack · Testing signals
pydantic/pydantic
Tests and CI were inspected, not executed; test existence establishes intended coverage, not passing results. The inspected suites use pytest, with separate native-core, documentation, plugin-installation, and static-type integration checks. CI defines platform and interpreter matrices, benchmarks, and downstream compatibility jobs. This inventory is bounded and does not establish exhaustive coverage or current coverage percentages.
- Root pytest configuration targets tests, treats warnings as errors, enables strict configuration, and disables benchmark timing by default; make test invokes coverage-backed pytest with configurable parallel threads.
- Inspected BaseModel tests assert missing-field/error payloads, invalid numeric inputs, Python/JSON dumps, and cyclic-input recursion errors.
- Serialization tests parameterize UUID, IP, secret, temporal, collection, Decimal, enum, and model outputs; core JSON tests assert partial parsing and base64 byte round-trips including invalid encoding.
- Function-call tests inspect preserved wrapper signatures, configuration-driven return validation, coercion in decorated constructors, and asynchronous return-validation failures.
- Plugin tests assert schema identity/settings and JSON success/error callbacks; the mutable installation fixture is marked thread-unsafe, and CI separately installs tests/plugin before running its integration suite.
- Core model tests directly construct SchemaValidator graphs and assert instance dictionaries, extras, and explicit-field tracking; CI defines core pytest and cargo test on Ubuntu, macOS, and Windows.
- Documentation tests discover and execute examples with platform/skip conditions and explicitly skip v1 docstrings; Mypy tests require --test-mypy, while CI separately invokes Pyright, Mypy, and Pyrefly integration targets. Coverage configuration omits deprecated and v1 modules.
- CI defines Python/platform matrices, CodSpeed workloads, scheduled family integration tests, dependency-boundary cases, and conditional downstream FastAPI tests; none supplies an executed result in this investigation.