skills.rest
wangke19
wangke19COMMUNITY
Explore all skills by this author →
GitHub

e2e-test

Automate end-to-end Kubernetes/OpenShift controller tests with Ginkgo/Gomega against a real cluster.

1|1|Updated Apr 11, 2026
Search Tags:#testing#e2e#kubernetes#controller#openshift#ginkgo#gomega
One-click install
npx skills add https://github.com/wangke19/my-claude-skills --skill e2e-test-wangke19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/wangke19/my-claude-skills/tree/main/plugins/ocp/skills/e2e-test
Command: npx skills add https://github.com/wangke19/my-claude-skills --skill e2e-test-wangke19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write E2E tests for Kubernetes/OpenShift controllers using Ginkgo/Gomega against a real cluster. Covers full resource lifecycle (create → update → delete), async reconciliation with Eventually(), finalizer cleanup, and error scenarios. Use when adding or modifying E2E tests for controllers, debugging flaky E2E tests, or setting up a new E2E test suite. Trigger on "write e2e test", "add integration test", "test controller on cluster", "ginkgo test", or "eventually assertion". Do NOT use for unit tests (use ocp:operator-dev) or OTE-based OpenShift tests. allowed-tools: Bash(), Read(), Glob(), Grep(), Agent(*)

Quick Start

Run the E2E test protocol against a real Kubernetes/OpenShift cluster to validate controller behavior.

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I write e2e tests for Kubernetes controllers using Ginkgo and Gomega?▼

To write e2e tests for Kubernetes controllers, use Ginkgo and Gomega against a real cluster to validate full resource lifecycles, async reconciliation with Eventually(), finalizer cleanup, and error scenarios.

How do I test asynchronous reconciliation and finalizer cleanup in OpenShift controllers?▼

Test asynchronous reconciliation and finalizer cleanup in OpenShift controllers by applying structured test patterns with Eventually() assertions against a real cluster to validate create, update, and delete flows.

Do I need a real Kubernetes cluster to run Ginkgo e2e tests for controller workflows?▼

Yes, you need a real Kubernetes cluster because e2e tests validate full resource lifecycles and asynchronous reconciliation that require actual cluster execution and structured test patterns with proper cleanup.

What is the best way to debug flaky e2e tests for Kubernetes controllers?▼

The best way to debug flaky e2e tests for Kubernetes controllers is to review your Ginkgo and Gomega structured test patterns, ensuring Eventually() assertions and proper cleanup handle asynchronous reconciliation correctly.

When should I not use Ginkgo e2e tests for my OpenShift controller?▼

You should not use Ginkgo e2e tests for unit testing OpenShift controllers or OTE-based OpenShift tests; use operator-dev for unit tests and reserve e2e tests for real cluster resource lifecycle validation.

Related Skills

Explore More Software Engineering Skills→
deandumdeandum
3

go/testing-with-framework

Write structured Go tests using Ginkgo and Gomega BDD-style syntax.

Community
Advanced
apacheapache
6.1k

flaky-analyze

Analyze flaky GitHub Actions CI failures for Pinot test classes.

Official
Advanced
hawkli-1994hawkli-1994
1

k8s-operator

Automate Kubernetes operator lifecycle management with Kubebuilder scaffolding and reconciliation logic.

Community
Advanced
htooayelwinicthtooayelwinict

testing

Automate TDD workflows across Pest, Vitest, and Playwright test layers.

Community
Advanced