Untested export
What an untested-export finding of fallow health means, why it matters and how to fix it.
What it reports
Runtime-reachable export has no test dependency path.
Health explains how fallow finds it.
Why it matters
No test reaches the export. A change to its behavior can break the production code that uses it, and no test fails.
Example
src/cart.ts calls roundCents from src/money.ts. test/money.test.ts imports only formatPrice from that file, so no test reaches roundCents.
Fix
Add or wire a test that imports the runtime path, or update entry-point/test discovery if the existing test is invisible to fallow.
Facts
| Fact | Value |
|---|---|
| Issue type | untested-export |
| Rule id in SARIF output | fallow/untested-export |
| Command | fallow health |
| Default severity | off |
| Filter option | --coverage-gaps |
| Suppression comment | // fallow-ignore-file coverage-gaps |
Fixable with fallow fix | No |
| Opt-in | Yes |