controller-tests

A specialist guide for writing integration tests for Kubernetes controllers, which automatically manage Kubernetes resources. It uses a test API server and Go testing libraries.

In plain words
What is it for?
Finding missing tests and covering reconciliation, finalizers, status changes, cross-namespace references, conflicts, and error handling with envtest, Ginkgo, and Gomega.
Why use it?
It helps test the controller's real reconciliation behavior, including asynchronous updates and failure paths, instead of checking only isolated functions.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/kuadrant/mcp-gateway/controller-tests
Clone the repo
git clone --depth 1 https://github.com/Kuadrant/mcp-gateway

Made for: Claude Code.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.01189
Opus 5 $0.00009 $0.00594
Sonnet 5 $0.00004 $0.00238
Haiku 4.5 $0.00002 $0.00119

Measured 2d ago against content hash e8fcaa2626e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

controller-tests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/controller-tests.md · 157 lines

How it starts

The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When invoked:

Context

You are writing integration tests for Kubernetes controllers using:

  • envtest: Provides a real API server for testing without a full cluster
  • Ginkgo v2: BDD testing framework
  • Gomega: Assertion library with Eventually/Consistently for async checks

Workflow

  1. Analyze the controller: Read the controller file specified in $ARGUMENTS (default: look for *_controller.go files in internal/controller/)

  2. Check existing tests: Read the corresponding *_controller_test.go file and suite_test.go to understand:

    • How the test suite is set up (manager, clients, field indexes)
    • Existing test patterns and helpers
    • Build tags used (e.g., //go:build integration)
  3. Identify test gaps: Based on the controller's Reconcile logic, identify untested scenarios:

    • Happy path reconciliation
    • Finalizer add/remove
    • Status condition updates
    • Cross-namespace references (ReferenceGrant)
    • Conflict detection
    • Error handling paths
  4. Write tests following these patterns:

Timeout Constants

Define timeout constants at the package or file level:

const (
    TestTimeout       = 10 * time.Second
    TestRetryInterval = 100 * time.Millisecond
)

Test Structure

Context("When <scenario>", func() {
    // Constants for this context
    const resourceName = "test-<scenario>-resource"

    // Typed names
    typeNamespacedName := types.NamespacedName{
        Name:      resourceName,
        Namespace: "default",
    }

    // Helper functions
    BeforeEach(func() {
		createTestGateway(ctx, gatewayName, "default")
		createTestMCPGatewayExtension(ctx, resourceName, "default", gatewayName, "default")
	})

	AfterEach(func() {
		deleteTestMCPGatewayExtension(ctx, resourceName, "default")
		deleteTestGateway(ctx, gatewayName, "default")
	})

    It("should <expected behavior>", func() {
        // Test body
    })
})

Cache Synchronization Pattern

When using a manager's cached client, always wait for cache sync before reconciling:

// Wait for cache to see the resource before reconciling
Eventually(func(g Gomega) {
    cached := &v1alpha1.MyResource{}
    g.Expect(testIndexedClient.Get(ctx, namespacedName, cached)).To(Succeed())
}, TestTimeout, TestRetryInterval).Should(Succeed())

_, err := reconciler.Reconcile(ctx, reconcile.Request{
    NamespacedName: namespacedName,
})
Expect(err).NotTo(HaveOccurred())

Read the full file on GitHub · 157 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 157 lines · 18 tokens per session scan A e8fcaa2626e7

Subscribe to this mod's changes

controller-tests is a command published in the GitHub repository Kuadrant/mcp-gateway (97 stars, last pushed 5d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,189 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.