integration-tests/

directory
v0.6.2 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Oct 2, 2026 License: MIT

README

Brewlet integration tests

Cross-component end-to-end harness for the Brewlet monorepo. This directory owns test orchestration and fixture applications. Production code, Kubernetes manifests, and specifications remain in their owning monorepo directories.

Layout

e2e/       runner, reset helper, shared library, and tiers 1-17
fixtures/  harness-owned Java demo applications and PetClinic build fixture

Running from the monorepo

From the repository root, run:

integration-tests/e2e/run.sh --tier 1 --tier 2

The harness defaults to core/ and kubernetes/ in the monorepo. The BREWLET_CORE_DIR and BREWLET_KUBERNETES_DIR overrides remain available for testing external checkouts.

Running

integration-tests/e2e/run.sh                 # all 17 tiers
integration-tests/e2e/run.sh --list          # tier catalog
integration-tests/e2e/run.sh --tier 4        # one tier
integration-tests/e2e/run.sh --reset         # remove Brewlet test state
integration-tests/e2e/run.sh --reset --tier 10
E2E_WORK=/tmp/brewlet-e2e integration-tests/e2e/run.sh --tier 9

Tiers skip when an optional host prerequisite is unavailable and fail only when an exercised capability fails. The suite covers:

Tier Scope Primary components
1 Go unit/component suites core + Kubernetes
2 CLI push, inspect, run, bundle, classpath, and JPMS core + fixtures
3 shim to runc under Linux cgroups core + fixtures
4 operator control plane and Helm packaging Kubernetes
5-6 host and in-cluster admission webhooks Kubernetes
7 Spring PetClinic artifact, layered deployment, runc, reconcile both + fixtures
8-9 AppCDS lifecycle, cross-namespace cache isolation, and serving through kubelet/CRI core + fixtures
10-11 installed Helm stack and webhook resilience Kubernetes
12 runnable image pulled and unpacked by kubelet core + fixtures
13 NodeProfile lifecycle Kubernetes
14 custom JDK + jaz NodeProfile, live workload, and broken-launcher readiness failure both + fixtures
15 live opt-in Prometheus metrics through Helm, provisioner, shim, and exporter both + fixtures
16 SPECIFICATION §14 failure modes on a live node core + fixtures
17 default-enabled runnable-stage GC: chart defaults, upgrade gate, reference protection, and reclamation both + fixtures

See AGENTS.md for cluster requirements, cleanup, and troubleshooting.

Monitoring runs from the GitHub Copilot app

The project extension in .github/extensions/e2e-monitor/ adds an Integration tests canvas. It starts run.sh tiers, the live HPA/admission scenarios, or the offline safeguard tests as detached processes, and shows per-tier progress and ETA, assertion results, failures, a live log, and the E2E_WORK artifacts. Run records are kept in the session's state directory under e2e-runs/, so they survive extension reloads.

When the selected kube context is a live cluster (anything other than Docker Desktop, kind, k3d, minikube, Rancher Desktop, OrbStack or Colima), the canvas shows a Node pool picker listing the cluster's pools and their Ready nodes, defaulting to javaworkers. The run gets E2E_NODE_ACCESS=kubectl and E2E_POOLS=<pool> automatically. Values set in Environment overrides win.

Kubernetes CLI API integration

The process/API integration suite lives in the existing Kubernetes Go module so it can reuse envtest and the production controllers:

make -C kubernetes test-cli-integration

It builds the CLI and invokes real kubectl/Helm against a fresh API server and etcd using only private fixture kubeconfigs. No Docker daemon, existing cluster, or tier reset is used. Missing prerequisites fail this explicit target. The Kubernetes pull-request CI job runs the same tests.

See CLI integration tests for coverage and limitations. In particular, fixture readiness and node inventory are simulated; this is not coverage of host provisioning or JVM execution.

Directories

Path Synopsis
e2e
live command
This deliberately untrusted competing verifier is used only to prove that its success cannot replace Brewlet verification and its failure cannot veto it.
This deliberately untrusted competing verifier is used only to prove that its success cannot replace Brewlet verification and its failure cannot veto it.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL