What problem does it solve?
Writing and maintaining reliable functional (end-to-end) tests for the Astronomer Private Cloud Helm chart requires navigating complex Kubernetes cluster setup, testinfra patterns, kubeconfig management, and cross-scenario test organization, which can lead to inconsistent tests, flaky runs, and wasted developer time.
Core Features & Use Cases
- Multi-scenario test organization: Structured guidance for writing tests for unified, control, and data plane installation configurations, plus shared cross-scenario tests.
- Kubernetes testing utilities: Built-in patterns for using testinfra, Kubernetes API clients, and project-specific kubeconfig helpers to write robust runtime assertions.
- Flaky test mitigation: Established conventions for marking and handling eventually-consistent cluster state during test runs.
Use case: A DevOps engineer can use this skill to quickly write a test that verifies all Astronomer containers run as non-root users across all installation scenarios, following project best practices and avoiding common errors like incorrect kubeconfig paths.
Quick Start
Use the functional-tests skill to write a new test that verifies the Prometheus container runs as the expected non-root user for the unified installation scenario.