aigw-contrib-e2e

Run end-to-end tests for Envoy Gateway and AI Gateway on Kubernetes clusters.

3|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/missBerg/envoy-skills --skill aigw-contrib-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aigw-contrib-e2e
Source: https://github.com/missBerg/envoy-skills/tree/main/ai-gateway/contributors/skills/aigw-contrib-e2e
Command: npx skills add https://github.com/missBerg/envoy-skills --skill aigw-contrib-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write end-to-end tests that verify Envoy Gateway and AI Gateway behavior on real Kubernetes clusters, ensuring reliability across deployments and feature sets.

Core Features & Use Cases

  • End-to-end test suites covering setup, manifests, mock providers, and streaming scenarios.
  • Reusable utilities for cluster provisioning, test execution, and resource teardown.
  • Structured test artifacts including kind clusters and feature-specific test files.

Quick Start

Launch the e2e test suite against your Kind cluster using the provided test harness and manifests.

Frequently Asked Questions about aigw-contrib-e2e

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

FAQPage Schema
How do I run end-to-end tests for AI Gateway in a Kubernetes environment?

End-to-end testing for AI Gateway requires a Go test suite with the test_e2e build tag. You execute these tests against a live kind-based Kubernetes cluster, applying manifests and mock providers to verify functionality across multiple features.

What do I need to set up before testing Envoy Gateway and AI Gateway?

Testing AI Gateway requires kind cluster tooling including kind, helm, and kubectl. You also need a Go test suite with the test_e2e build tag and testdata manifests to provision the cluster environment.

How do mock providers work when testing AI Gateway streaming scenarios?

Mock providers simulate backend AI services during testing to validate AI Gateway streaming scenarios. They allow the end-to-end test suite to verify feature-specific behaviors without relying on real external API endpoints.

What is the best way to validate AI Gateway behavior across different Kubernetes deployments?

Validating AI Gateway behavior across deployments is best achieved through automated end-to-end tests. They provision kind-based clusters, apply manifests, and execute structured test cases to ensure reliability across streaming and feature sets.

Does this e2e testing framework support live Kubernetes clusters or only local kind environments?

The e2e testing framework targets live Kubernetes environments using kind-based clusters. It provisions the cluster, applies testdata manifests, and tears down resources to test Envoy Gateway and AI Gateway behavior reliably.