base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Test the release launcher behavior

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-08 16:41:23 +00:00
parent 012af5e80a
commit f9ec143130
2 changed files with 413 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/roadmap/implementation.md
View File

@@ -240,7 +240,7 @@ publication to the module-selected native CLI. Commit the stage.
## Stage 3: cover launcher behavior with fast offline tests
**Status:** pending. **Prerequisite:** Stage 2.
**Status:** complete. **Prerequisite:** Stage 2.
**Files:** `scripts/release_test.go`, plus launcher corrections found by the
tests and stage evidence in this plan. Use a tests-only external Go package such
@@ -278,6 +278,13 @@ as `release_test`; add no production Go file or exported helper API.
the default offline suite with the Stage 1 environment. None of these tests
compiles a real publisher or contacts a service.
Observed 2026-10-08: `gofmt -d scripts/release_test.go` reported no changes.
`go test -mod=readonly -count=1 ./scripts` passed. The offline default
`go test -mod=readonly -count=1 ./...` passed for the library, internal adapter,
examples, and scripts package. The tests use only temporary fixtures and a
controlled Go executable; they do not build the real publisher or contact a
service.
**Completion:** the small launcher has regression coverage for its own parsing,
path, build, and delegation responsibilities. Commit the stage.