Skip to content

ci: broaden test workflow to run the full go test ./... suite - #3

Merged
ZacxDev merged 1 commit into
feat/label-retriggerfrom
zach/broaden-test-ci
Jul 6, 2026
Merged

ci: broaden test workflow to run the full go test ./... suite#3
ZacxDev merged 1 commit into
feat/label-retriggerfrom
zach/broaden-test-ci

Conversation

@ZacxDev

@ZacxDev ZacxDev commented Jul 6, 2026

Copy link
Copy Markdown

What

Broadens the existing .github/workflows/test.yml test step to run the whole suite. build.yml is untouched.

Before:

go test ./pkg/... -v
go test ./controllers/... -run TestNextSourceBranches -v

After:

go test ./... -v

(go build ./... unchanged; Go pinned at 1.19 per go.mod.)

Why

The narrow test step missed the newly-added api/v1alpha1 tests and most of the controllers tests (store-decision, label-folding, churn-guard, reconcile fake-client paths). Broadening to ./... makes those gate future PRs.

Safe without envtest: the new controllers tests use the controller-runtime fake client, and the Ginkgo TestAPIs suite has no specs (runs 0 of 0 → SUCCESS) so it passes trivially without KUBEBUILDER_ASSETS. The stale comment claiming the controllers suite needs envtest is replaced.

Local verification

In a clean worktree (Go 1.25 locally; the workflow pins 1.19):

  • go build ./... → OK
  • go test ./... -vgreen end-to-end, 0 failures. api/v1alpha1 (4 funcs), controllers (7 funcs incl. the 0-spec TestAPIs), pkg/git (5 funcs) all ok.
  • test.yml parses as valid YAML.

🤖 Generated with Claude Code

The workflow previously ran only ./pkg/... and a single -run
TestNextSourceBranches in ./controllers, missing the new api/v1alpha1
tests and the other controllers tests (store-decision, label-folding,
churn-guard, reconcile fake-client paths).

Switch the test step to go test ./... -v. Safe without envtest: the
controllers tests use the controller-runtime fake client and the Ginkgo
TestAPIs suite has no specs (passes trivially without KUBEBUILDER_ASSETS).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ZacxDev
ZacxDev merged commit 0a165f3 into feat/label-retrigger Jul 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant