TL;DR
Four files in the directive test suite contain 4-5 placeholder assertions each — expect(true).toBe(true) after a render call, with no actual assertion on the rendered output. The tests pass when the directive doesn't throw, but no semantic check verifies the output is correct. They look like in-progress tests that were never finished.
Locations
test/directives/layouts.test.ts:79, 188, 293, 421 (4 placeholders)
test/directives/outputs.test.ts:48, 82, 113, 185 (4 placeholders)
test/directives/auth.test.ts:69, 131, 231, 306 (4 placeholders)
test/directives/comments.test.ts:41, 89, 131, 174, 223 (5 placeholders)≈19 placeholder assertions across the four files.
Why it matters
The placeholders give the impression of coverage:
bun testreports them as passing- Coverage tools count the test as exercising the file
- A regression in any of those directives would only surface if it threw a hard error during processing — silent output errors (wrong markup, missing wrapper, escaped HTML) wouldn't be caught
Worse: a future contributor reading the test file sees a pattern of "render then expect(true).toBe(true)" and may follow the convention when adding new tests, propagating the noise.
Proposed action
Two paths:
Fill them in — replace each placeholder with a real assertion against the rendered output. For layouts/outputs/auth/comments, the actual rendered string is what should be checked. ~30 min of work per file.
Delete them — if the surrounding test already asserts the output somewhere, the placeholder is redundant; if not, deleting just removes the false-coverage signal. Either way, an honest "this directive is untested" is more useful than a green-but-empty test.
I'd lean toward filling them in for outputs.test.ts (these are the @text, @html, etc. directives — high-value to keep tested) and deleting in layouts.test.ts / auth.test.ts (sub-features that have other test files covering them).
Companion finding
The audit also flagged a few "structural-only" tests that assert a function exists but never call it — same shape of false-coverage. Worth searching for toHaveProperty / typeof X === 'function' patterns that aren't followed by an actual invocation:
packages/components/test/composables.test.ts:10-14
expect(result).toHaveProperty('copy')
// … but never calls result.copy()
packages/stx/test/database.test.ts
typeof sb.create === 'function'
// … but never invokes sb.create()Found during a deep-scan audit.
🤖 Filed via Claude Code