Conformance Dashboard¶

This page summarizes the external conformance and end-to-end corpus checks that CI runs for datamodel-code-generator. The table is generated from tox.ini, .github/workflows/test.yaml, local runner scripts, and JSON-Schema-Test-Suite pytest metadata.

These suites are compatibility and coverage signals. They show that CI exercises datamodel-code-generator against pinned upstream corpora; they do not claim complete specification compliance.

Suite name	Input format / scope	Source corpus or upstream project	Local runner script	tox environment	CI job name	Expected corpus size/count	External checkout/network in CI	What the suite proves
W3C XML Schema Test Suite	XML Schema (`.xsd`) generation from valid schema documents	w3c/xsdtests @ `7bc3365c652a322f3d762021b3879eb92dae7e30`	`scripts/run_w3c_xmlschema_e2e.py`	`w3c-xmlschema-e2e`	`W3C XML Schema e2e` (`w3c-xmlschema-e2e`)	5,284 valid schemaDocument entries; 5,283 unique valid schemaDocument paths	Yes; cached external checkout, network on cache miss	CI exercises XML Schema generation against valid schema documents in the pinned W3C test suite and imports the generated Python modules.
JSON-Schema-Test-Suite	JSON Schema generated Pydantic v2 model validation for configured drafts	json-schema-org/JSON-Schema-Test-Suite @ `fe8c2f0de2041943975932b6bf4bd882625b6cfb`	`scripts/run_jsonschema_suite_conformance.py`	`jsonschema-suite-conformance`	`JSON-Schema-Test-Suite conformance` (`jsonschema-suite-conformance`)	640 groups / 2,226 tests for default drafts `draft7`, `draft2020-12` (asserted by pytest)	Yes; external checkout cloned during the CI job	CI exercises generated Pydantic v2 models against JSON-Schema-Test-Suite expectations for the configured drafts, with unsupported cases classified in tests.
AsyncAPI spec JSON Schemas	Stable AsyncAPI specification JSON Schema files used as JSON Schema input	asyncapi/spec-json-schemas @ `469c2b2bf5ed88e0cdf1e48975b93a87c710d229`	`scripts/run_asyncapi_spec_json_schemas_e2e.py`	`asyncapi-spec-json-schemas-e2e`	`AsyncAPI spec JSON Schemas e2e` (`asyncapi-spec-json-schemas-e2e`)	12 schemas	Yes; cached external checkout, network on cache miss	CI exercises generation and import of Python models from stable AsyncAPI specification JSON Schema files, including local handling of HTTP references.
Apache Avro schema pass corpus	Apache Avro schema pass files from the upstream C test corpus	apache/avro @ `9110c693767c1dde2665b2b57939333478b12036`	`scripts/run_apache_avro_schema_pass_e2e.py`	`apache-avro-schema-pass-e2e`	`Apache Avro schema pass e2e` (`apache-avro-schema-pass-e2e`)	28 schemas	Yes; cached external checkout, network on cache miss	CI exercises Avro generation against upstream pass-corpus schemas and imports the generated Python module.
Protocol Buffers official corpus	Official Protocol Buffers `.proto` files selected by the local runner	protocolbuffers/protobuf @ `4376cba55d9e2f44f7e317d9c10e0259d145f8cf`; sparse checkout: `src`, `conformance`, `benchmarks`	`scripts/run_protobuf_official_e2e.py`	`protobuf-official-e2e`	`Protocol Buffers official e2e` (`protobuf-official-e2e`)	65 schemas	Yes; cached external checkout, network on cache miss	CI exercises Protocol Buffers generation against supported files in the pinned official corpus subset and imports the generated Python module.

Generated Sources¶

tox environments and runner script paths are derived from tox.ini.
CI job names, upstream checkout pins, cache usage, and workflow --expected-* arguments are derived from .github/workflows/test.yaml.
JSON-Schema-Test-Suite default draft counts are derived from tests/main/payload_validation/json_schema_suite.py because the workflow delegates count assertions to pytest.