Repository navigation
Specs with no tests cannot be proven: add real tests to 46 specs #7642
Description
Goal
About 46 specs added by merged PRs have no tests, so a seal records total == 0 and proves nothing. Under the Queen coverage rule (a closed issue counts when its specs are sealed with passed == total > 0) their issues stay uncovered. Each spec needs at least one real test that exercises its decisions; a vacuous assert does not count.
Specs
specs/functions/neuro-image-generate.t27specs/functions/render-avatar-video-run.t27specs/tools/mcp/gitbutler.t27specs/tools/mcp/needle.t27specs/tools/mcp/neon.t27specs/tools/mcp/notebooklm.t27specs/tools/mcp/railway-mcp-server.t27specs/tools/mcp/t27-traceability.t27specs/tools/tri/gen.t27specs/tools/tri/harness.t27specs/tools/tri/health.t27specs/tools/tri/hooks.t27specs/tools/tri/issues.t27specs/tools/tri/jumps.t27specs/tools/tri/kinds.t27specs/tools/tri/lean.t27specs/tools/tri/ledgers.t27specs/tools/tri/loop.t27specs/tools/tri/merging.t27specs/tools/tri/misread.t27specs/tools/tri/mods.t27specs/tools/tri/mutate.t27specs/tools/tri/now.t27specs/tools/tri/one-away.t27specs/tools/tri/orphaned.t27specs/tools/tri/pr.t27specs/tools/tri/prose.t27specs/tools/tri/quantifiers.t27specs/tools/tri/red.t27specs/tools/tri/reseal.t27specs/tools/tri/rtl.t27specs/tools/tri/seals.t27specs/tools/tri/serve.t27specs/tools/tri/skill.t27specs/tools/tri/status.t27specs/tools/tri/sweep.t27specs/tools/tri/vsim.t27specs/tools/tri/window.t27specs/tools/tri/worktrees.t27specs/tools/trinity/tri/mesh.t27specs/tools/trinity/tri/needle-check.t27specs/tools/trinity/tri/needle-search.t27specs/tools/trinity/tri/needle.t27specs/tools/trinity/tri/omega.t27specs/tools/trinity/tri/particles.t27specs/tools/trinity/tri/phi.t27
Success Criteria
Per spec: at least one test with runtime asserts executed (t27c test-report shows more than 0), sealed with passed == total > 0.
Scope note
Tests only; the behaviour in the specs does not change.
User Scenarios
- Given a spec file with zero tests, when the spec is compiled and tested with
t27c, then the test report showstotal == 0and the seal cannot prove the spec. - Given each of the 46 cited specs, when a real test exercising its decisions is added and
t27c sealruns, then the seal recordspassed == total > 0. - Given the Queen coverage rule, when all 46 specs have sealed tests with
passed == total > 0, then their associated issues become covered.
Requirements
- FR-001: Each cited spec file MUST contain at least one test case that executes runtime asserts against the spec's decisions.
- FR-002: Added tests MUST NOT be vacuous asserts; they MUST exercise observable behavior defined by the spec.
- FR-003: After changes,
t27c test-reportfor each spec MUST showtotal > 0. - FR-004: Each spec MUST seal with
passed == total > 0viat27c seal. - FR-005: The behavior specified in each .t27 file MUST NOT change; only test additions are allowed.
Success Criteria
t27c test-report specs/functions/neuro-image-generate.t27showstotal > 0and exits 0t27c test-report specs/functions/render-avatar-video-run.t27showstotal > 0and exits 0t27c test-report specs/tools/mcp/gitbutler.t27showstotal > 0and exits 0t27c test-report specs/tools/mcp/needle.t27showstotal > 0and exits 0t27c test-report specs/tools/mcp/neon.t27showstotal > 0and exits 0t27c test-report specs/tools/mcp/notebooklm.t27showstotal > 0and exits 0t27c test-report specs/tools/mcp/railway-mcp-server.t27showstotal > 0and exits 0t27c test-report specs/tools/mcp/t27-traceability.t27showstotal > 0and exits 0t27c test-report specs/tools/tri/gen.t27showstotal > 0and exits 0t27c test-report specs/tools/tri/harness.t27showstotal > 0and exits 0t27c test-report specs/tools/tri/health.t27showstotal > 0and exits 0t27c test-report specs/tools/tri/hooks.t27showstotal > 0and exits 0- All 46 cited specs seal with
passed == total > 0viat27c seal(46 seals)
Boundary
- specs/functions/neuro-image-generate.t27
- specs/functions/render-avatar-video-run.t27
- specs/tools/mcp/gitbutler.t27
- specs/tools/mcp/needle.t27
- specs/tools/mcp/neon.t27
- specs/tools/mcp/notebooklm.t27
- specs/tools/mcp/railway-mcp-server.t27
- specs/tools/mcp/t27-traceability.t27
- specs/tools/tri/gen.t27
- specs/tools/tri/harness.t27
- specs/tools/tri/health.t27
- specs/tools/tri/hooks.t27
Activity
dmitrii-f-t27 commentedon Oct 10, 2026
Done on
master— every spec listed here now has real tests and a seal withpassed == total > 0. Closing as completed.Checked on
masterat 295b2c5 (2026-10-10).I built t27c from that tree (
cargo build --release --manifest-path bootstrap/Cargo.toml, zig 0.16.0) and ran these two commands on each of the 46 specs:t27c test-report <spec> --specs-dir specs: 147/147 tests pass, 0 fail, 0 vacuous passes. Every test executed at least one runtime assert.t27c seal <spec> --verify: 46/46all hashes MATCH. In each committed seal,tests.passed == tests.total > 0andfailed == 0.Where the tests landed (all merged by @gHashTag; none of these PRs referenced this issue, so it stayed open):
specs/functions/specs/tools/mcp/specs/tools/tri/gen…mergingspecs/tools/tri/misread…redspecs/tools/tri/reseal…worktreesspecs/tools/trinity/tri/Not covered by this check: I did not wait for a separate CI run of these specs on that
masterSHA. The results above come from a local run of t27c built from that exact tree.Dmitrii Fedorov (@dmitrii-f-t27)