Repository navigation
feature: expand e2e coverage across CLI surface #39
Description
e2e already covers cluster up / status / down, plus fixture steps for deploy, run, logs, and delete (scenarios/task-migrate-smoke/e2e.yaml).
These can still regress against a live cluster:
cluster kubeconfig(path and--raw)plan(offline and live)list/statusafter deployresolveagainst a fixture
Add cases on the shared Kind cluster, not a second create/destroy cycle. Prefer new scenarios/*/e2e.yaml steps when the command fits the closed ops (deploy / run / logs / delete). Commands that do not fit stay as suite methods on E2ESuite.
Offline golden tests stay in integration. Grow incrementally. Do not hit every flag in one giant test.
Activity
atkrad commentedon Jul 27, 2026
Note: parent #37 now uses
testify/suite(E2ESuite). Expanding CLI coverage means adding methods to that suite (or a sibling suite in the same package). No new cluster create/destroy per command -- they all shareSetupSuite's cluster ands.kcPath.