test: align Claude and Codex plugin E2E gateways - #1041
Conversation
Signed-off-by: Will Killian <wkillian@nvidia.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 10 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (1)
🧰 Additional context used📓 Path-based instructions (1)Review automation changes for reproducibility, pinned versions where appropriate, secret handling, and consistency with the documented validation matrix.⚙️ CodeRabbit configuration file Files:
WalkthroughThe Claude and Codex plugin E2E scripts now use gateway port ChangesE2E harness updates
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Other Merge Risk: ⚪ Minimal · up to The E2E harness updates match the documented gateway and workspace contracts and are mergeable. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Signed-off-by: Will Killian <wkillian@nvidia.com>
Overview
Align the Claude Code and Codex plugin E2E fixtures with the documented persistent Relay gateway lifecycle, current sidecar-reuse behavior, and their test-owned observability output.
Details
127.0.0.1:47632, rather than generating an MCP-only test port.Where should the reviewer start?
Review
scripts/test-claude-plugin-e2e.shandscripts/test-codex-plugin-e2e.sh, focusing on endpoint setup, sidecar lifecycle, and test-owned ATOF paths.Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
Summary by CodeRabbit