You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
t27c test: execute assertions, not just count declarations (t27#11730) #11805
t27c test only counted test/invariant/bench declarations and exited 0 even for a spec with assert always_one() == 999 (always false). This is the false-green trap (t27#11730). The fix: generate the Zig and run zig test when the generated Zig compiles; non-compiling specs keep the legacy declaration-only result (backward compat).
Acceptance criteria
With a false assertion planted, t27c test <spec> exits non-zero.
With the plant removed, the same command exits 0.
Specs whose generated Zig does not compile keep exiting 0 (no regression for declaration counting).
Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.
missing: ## User Scenarios -- at least one Given/When/Then scenario
missing: ## Requirements -- numbered obligations, FR-001: ... MUST ...
Activity
github-actions commentedon Oct 23, 2026
Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.
FR-001: ... MUST ...fix(t27c): t27c test now executes assertions via zig test (Closes #11805
test: the zig-test pass compacted -- closure for the verbose lists, t…
test: the budget discipline applied to the zig-test pass -- doc block…
t27c test: execute assertions via zig test (Closes #11805) (#11806)