Creating a New Java E2E Test with a Replay Proxy YAML Snapshot

This skill covers the complete workflow for adding a new Java failsafe integration test backed by a handcrafted YAML snapshot for the replay proxy.

Overview

The Java E2E tests use a replay proxy (test/harness/replayingCapiProxy.ts) that intercepts HTTP calls to the Copilot API and returns pre-recorded responses from YAML snapshot files. This avoids needing real authentication in CI.

Key constraint: Java's CapiProxy.java always sets GITHUB_ACTIONS=true (line 104), which forces the replay proxy into read-only mode. You cannot record snapshots by running Java tests — you must handcraft the YAML.

Step-by-Step Workflow

Step 1: Choose a snapshot category and snapshot base name