E2E Test Cases

Concrete, repeatable end-to-end test cases for specific Magda features, run against a real cluster (e.g. minikube). Most are API-level and build on the shared setup in Feature-specific testing through the gateway with an API key (expose the gateway to the host, then authenticate with an API key — optionally as a purpose-built test user). Some cases exercise a different surface (the mgd CLI, an agent skill, or the Web UI) and document their own local setup.

Each case is self-contained: it lists what it verifies, how to run it (prefer a scripted, assertion/checksum-based driver), and how to clean up.

Cases

• DB TLS + non-default privileged user
• sslmode=verify-full server-certificate verification against a simulated managed database
• Large file storage (multipart upload + Range download)
• mgd CLI (auth, search, dataset/dist CRUD, large-file round-trip)
• mgd agent skill auto-use
• Distribution version aspect in the Web UI
• In-cluster PostgreSQL wal-g cross-version backup / restore (roll-forward + PITR)
• In-cluster PostgreSQL major upgrade (PG 13 → 17 logical dump / restore)
• Migrate the in-cluster PostgreSQL to a managed/cloud database (Pathway B)
• Fresh install on PostgreSQL 17 — client authentication (SCRAM)
• DB migrator surfaces the PG15+ public-schema privilege failure (and classifies a missing database locale-independently)

Adding a new case

• Add a *.md file here describing the case and (ideally) referencing a scripted driver checked into the relevant component.
• Link it from this index and, if broadly useful, from End-to-End Full Cluster Deployment Test.
• Reuse the shared gateway + API-key setup rather than repeating it; only document what’s specific to the feature under test.