Skip to content

test: report missing kubectl checks as skipped - #1243

Merged
jayminwest merged 1 commit into
jayminwest:mainfrom
low-country-cyber:fix/kubectl-manifest-test-skip
Sep 4, 2026
Merged

test: report missing kubectl checks as skipped#1243
jayminwest merged 1 commit into
jayminwest:mainfrom
low-country-cyber:fix/kubectl-manifest-test-skip

Conversation

@joerosbury

Copy link
Copy Markdown
Contributor

Summary

  • detect kubectl availability once when the manifest test module loads
  • register the two kubectl-dependent checks with test.skipIf(...)
  • preserve the existing manifest assertions when kubectl is available

Previously, when kubectl was unavailable, the two tests printed a warning
and returned normally. Bun and JUnit therefore reported those checks as
passing instead of skipped.

Validation

Without kubectl:

  • 1 passed
  • 2 skipped
  • 0 failed
  • JUnit reports skipped="2"

With checksum-verified kubectl v1.37.0 available:

  • 3 passed
  • 0 failed
  • all manifest assertions executed

Repository validation:

  • Warren pre-commit gates: 12/12 passed
  • git diff --check: passed

The two optional Linux+bwrap sandbox tests were skipped in the controlled
validation environment because bwrap was intentionally unavailable; no
bwrap-related source changes are included in this PR.

Fixes #1233

@jayminwest
jayminwest merged commit 0469c13 into jayminwest:main Sep 4, 2026
5 checks passed
@jayminwest

Copy link
Copy Markdown
Owner

Great work @joerosbury, thanks for the PR!

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.

kustomize manifest test passes silently when kubectl is missing

2 participants