functional-tests

Create and execute functional end-to-end tests for Astronomer Private Cloud Helm charts using Kubernetes API and testinfra utilities.

490|98|Updated Jan 15, 2018
One-click install
npx skills add https://github.com/astronomer/astronomer --skill functional-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: functional-tests
Source: https://github.com/astronomer/astronomer/tree/main/.agents/skills/functional-tests
Command: npx skills add https://github.com/astronomer/astronomer --skill functional-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about functional-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write functional end-to-end tests for Astronomer Private Cloud Helm charts?

To write functional end-to-end tests for Astronomer Private Cloud Helm charts, use structured guidance for testinfra runtime assertions and Kubernetes API clients, organizing tests across unified, control, and data plane installation scenarios.

How does testinfra work with Kubernetes for cluster setup validation?

Testinfra works with Kubernetes by applying runtime assertion workflows against the Kubernetes API, using project-specific kubeconfig helpers to validate cluster state and verify container configurations across different installation scenarios.

What is the best way to handle flaky tests in Kubernetes end-to-end testing?

The best way to handle flaky tests in Kubernetes end-to-end testing is to apply established conventions for marking and managing eventually-consistent cluster state during test runs, ensuring robust test execution.

Can I use this approach to test non-root user configurations across all installation scenarios?

Yes, you can write tests verifying non-root user configurations across unified, control, and data plane installation scenarios, following project best practices and avoiding common errors like incorrect kubeconfig paths.

Do I need a kubeconfig to run testinfra assertions on a Kubernetes cluster?

Yes, you need a valid kubeconfig to run testinfra assertions on a Kubernetes cluster, as proper kubeconfig management is required to interact with the Kubernetes API and execute functional tests correctly.

Why does functional testing for Astronomer APC require multi-scenario test organization?

Functional testing for Astronomer APC requires multi-scenario test organization to ensure consistent validation across unified, control, and data plane installations, preventing inconsistent tests and flaky runs during complex cluster setup.