test:run-kind

Execute end-to-end tests for the Kagenti platform on a local Kind Kubernetes cluster.

292|103|Updated Mar 27, 2025
One-click install
npx skills add https://github.com/kagenti/kagenti --skill test-run-kind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test:run-kind
Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/test%3Arun-kind
Command: npx skills add https://github.com/kagenti/kagenti --skill test-run-kind

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the execution of end-to-end tests within a local Kind Kubernetes cluster, enabling rapid validation and debugging of agent deployments.

Core Features & Use Cases

  • Local Testing: Run comprehensive E2E tests directly on your development machine.
  • CI Pre-validation: Quickly check code changes before pushing to the CI pipeline.
  • Debugging: Facilitates debugging of test failures by providing direct access to logs and cluster state.

Quick Start

Execute all end-to-end tests locally on your Kind cluster by running the provided script.

Frequently Asked Questions about test:run-kind

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

FAQPage Schema
How do I run E2E tests on a local Kubernetes cluster?

You can run E2E tests on a local Kubernetes cluster by executing automated scripts that deploy your agents to a Kind cluster and run pytest suites to validate functionality and deployment configurations.

Can I run specific filtered test suites instead of all E2E tests?

Yes, you can run specific filtered test suites by passing parameters to the pytest execution, allowing you to target individual agent functionalities rather than running the entire end-to-end test suite.

What is the best way to pre-validate code changes before pushing to CI/CD?

The best way to pre-validate code changes before CI/CD is to run end-to-end tests locally on a Kind cluster, ensuring deployment configurations work in a production-like environment before integration.

Does this approach support debugging test failures for Kubernetes deployments?

Yes, running E2E tests on a local Kind cluster facilitates debugging test failures by providing developers with direct access to cluster state and application logs for rapid troubleshooting.

Why use Kind for local Kubernetes testing?

Using Kind for local Kubernetes testing provides a production-like environment on your development machine, enabling rapid validation and debugging of agent deployments without remote cluster overhead.