Skip to content

feat: Phase J J9 schema-test cross-reference checker -- catches schema drift where schemas are added without tests, 63 tests - #897

Merged
cschanhniem merged 1 commit into
mainfrom
feat/j9-schema-test-coverage
Jul 10, 2026
Merged

cschanhniem merged 1 commit into
mainfrom
feat/j9-schema-test-coverage

Conversation

@cschanhniem

Copy link
Copy Markdown
Collaborator

Implements J9 from NEXT_100_PR_MAP: cross-reference checker between schemas and tests.

What

  • schema_test_coverage.py: check_schema_test_coverage() + format_schema_coverage_report() + SchemaCoverageReport + SchemaCoverageEntry
  • _find_test_references(): scans test files for schema name (including hyphen alias)
  • scripts/check_schema_test_coverage.py: runnable check with --warn-only flag
  • 63 tests; BASELINE 7465 to 7528

Why

The repo has 28 schemas. Without a cross-reference check, schemas can be added or modified without any test being updated — the gap is silent. This checker surfaces uncovered schemas so maintainers can add tests or document why a schema has no test.

Disconfirming pass

  • The checker does NOT enforce coverage (it's advisory with --warn-only default); enforcing it would block adding schemas that intentionally don't have direct unit tests
  • Schema name matching is case-insensitive and handles underscore/hyphen aliases
  • No safety/release policy changed; no calibration policy touched

…a drift where schemas are added without tests, 63 tests (#897)
@cschanhniem
cschanhniem merged commit 3946b35 into main Jul 10, 2026
1 check failed
@cschanhniem
cschanhniem deleted the feat/j9-schema-test-coverage branch July 10, 2026 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant