chore(e2e): tag suite traffic with x-client-type: test - #93
Merged
Conversation
|
✅ CI - Verify PASSED Commit:
|
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
1 participant
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.
Why
Estate test-traffic contract: every e2e/synthetic request must carry
x-client-type: test. The edge classifier (Traefik -> Vector) and@agentage/observabilityspan stamping key on exactly this header; UA sniffing is only a fallback. Untagged suite traffic lands in real-user SLIs whenever the suite is pointed at a deployed host viaLANDING_BASE_URL.What
packages/landing/e2e/playwright.config.ts:use.extraHTTPHeaderstags browser page loads andrequest-fixture calls (the whole suite goes through therequestfixture) in one place.Verified
prettier --checkclean;playwright test --listloads the config (36 tests). No suite run against a deployed host.