The single most reliable indicator of a pending regression is a pull request that modifies core business logic while modifying zero test files. Catalayer Code analyzes git tree deltas to detect and flag untested changes with deterministic precision.
Every production code change should be paired with a corresponding verification delta.
Static diff analysis detects missing test files without requiring test runner execution.
Changes to API routes, database models, and financial calculations require explicit test fixtures.
Detecting test gaps at the commit level prevents tech debt accumulation.
Specific verifiable repository conditions evaluated by Catalayer Code.
| SIGNAL NAME | VERIFIED REPOSITORY CONDITION | CONFIDENCE | TARGET RISK MITIGATED |
|---|---|---|---|
| Source-to-Test Delta Coupling | Source files modified with 0 modifications in tests/ or __tests__/ | HIGH | Unverified business logic deployed to production |
| Critical Path Exemption Check | Changes to auth, billing, or crypto paths without test assertion updates | HIGH | Security bypass and transactional calculation failure |
A repository may proudly report "85% line coverage" in its README badge, yet a developer can commit a 300-line change to the checkout calculation engine without adding a single test. The global coverage drops to 84.8%—barely noticeable—while the new feature is 100% untested.
Catalayer Code evaluates Delta Coverage: inspecting specifically what changed in the current commit.
What this inspection method does not and cannot evaluate.
Run deterministic checks against any public repository without granting OAuth permissions. Review structural gaps, untested changes, and reviewability findings with evidence.
Yes. Catalayer Code recognizes standard test file conventions across JavaScript/TypeScript (*.test.ts, *.spec.js), Python (test_*.py), Go (*_test.go), Rust (tests/), and Java (*Test.java).