Prove the edge's core guarantees with real traffic#228
Merged
Conversation
scotwells
force-pushed
the
test/edge-end-to-end-scenarios
branch
from
June 25, 2026 19:16
c0de345 to
0ea3023
Compare
Adds four end-to-end scenarios that send real traffic through the edge and confirm the promises customers depend on: the firewall enforces, an offline origin fails cleanly, the branded error page shows, and one bad certificate can't break its neighbors. Each asserts on a real response, not just that the control plane wrote the config. Includes a plain-language guide to how we test the edge and what we can't yet guarantee. These scenarios need the two-cluster production-fidelity environment, so they live under test/e2e-edge (separate from the single-stack test/e2e suite the default CI runs) and execute via `task test-infra:e2e` against that environment. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JbCy8vy66RdNYzGSgqH6P6
scotwells
force-pushed
the
test/edge-end-to-end-scenarios
branch
from
June 25, 2026 19:35
0ea3023 to
bc04aa9
Compare
This was referenced Jul 10, 2026
This was referenced Jul 13, 2026
scotwells
marked this pull request as ready for review
July 14, 2026 22:17
ecv
self-requested a review
July 14, 2026 22:33
ecv
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this proves
Four end-to-end tests that send real traffic through the edge and confirm the guarantees customers depend on:
Each test checks the outcome with a real request — the same thing a customer would experience — rather than confirming the control plane wrote the right configuration and assuming the edge followed.
It also adds a short, plain-language guide to how we test the edge: what each test guarantees, how we know a result is trustworthy, and — honestly — what we can't yet guarantee.
Why it matters
These are the promises the edge makes to customers. Proving them with real traffic, in an environment that mirrors production, is the difference between believing the edge works and knowing it does.
Builds on
The faithful test environment and the real-vs-intended config check opened alongside this. Together they let each test give a verdict from real traffic, backed by proof the edge was actually configured the way the test assumed.
Part of #247 — catching silent edge misconfiguration before it reaches customers.
One of a five-PR stack, best reviewed and merged in order: