test(justfile): run the CLI and debugger tests outside the coverage set

Assisted-by: DeepSeek V4.1 Flash
2026-09-20 01:40:51 +02:00
parent e836d6150d
commit 63562a503a
2 changed files with 15 additions and 0 deletions
@@ -84,6 +84,14 @@ jobs:
        # suites); the runner's Go setup provides both the tool and GOROOT.
        run: go test -count=1 -timeout 10m -coverprofile=coverage.out ./arch/... ./asm/... ./ast/... ./disasm/... ./format/... ./lexer/... ./lint/... ./lsp/... ./parser/... ./token/... ./verify/...

+      - name: Tests outside the coverage set
+        # The CLI and the debugger sit outside `packages` because a thin main and a
+        # ptrace-bound package pull the total under the floor, but their tests guard
+        # shipped surfaces: the command exit codes, the manual pages against the
+        # binary's own help, and the debugger's architecture-neutral units.  They run
+        # here so the floor stays a product measure and nothing is left untested.
+        run: go test -count=1 -timeout 10m ./cmd/... ./debug/...
+
      - name: Oracle parity
        # Re-run the live go-tool-asm comparison as its own step so that a parity
        # regression names the gate that failed instead of hiding inside the suite.