Repository navigation
proposal: Kind-based e2e layer (cluster lifecycle + deploy smoke) #37
Description
Offline integration goldens prove chart and spec rendering. They do not prove the live path: cluster up -> deploy -> workload Ready -> delete -> cluster down.
Shipped in #42: //go:build e2e under internal/e2e/. Kind via localkube (same stack as deployah cluster up). Drive the CLI in-process with nabattest.Run. Scenarios are directories under internal/e2e/testdata/ with deployah.yaml + expect.yaml. CI: nix run .#test-e2e.
Expectations are declared, not derived from the spec (so a naming bug is not mirrored). Use klient waits only; do not let e2e-framework create its own Kind cluster.
Follow-ups still open: #38 (HTTP reachability), #39 (broader CLI), #40 (compiled binary), #41 (pin/preload images).
Activity