optable-targeting smoke tests - #5
Open
justadreamer wants to merge 2 commits into
Open
Conversation
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.
A manual smoke test for the optable-targeting module against the live Optable edge.
./sample/optable-smoke-test.shruns three scenarios, each starting its own Prebid Server with its own config, postingsample/requests/optable-app-smoke.json(a mobile in-app request), then asserting on the response:na.edge.optable.coext.prebid.passthrough.optable.id5_signaturepresentca.edge.optable.coprocessed-auction-requesthook still enrichesThe two edges hold different data for the
prebidtesttenant, so expectations differ per scenario rather than being uniform:naresolves an ID5 signature but returns an empty audience,careturns audience segments but no ID5. Between them both halves of what the module renders are covered. Each scenario also asserts the negative, so an unexpected signature or keyword fails the run.The two split-plan scenarios additionally verify that pubmatic, pinned at
0inbidder-enrichment-percentages, is never enriched.Also adds the configs the scenarios need (
-ca,-legacy-plan) and enables the bidders the sample request names.Notes:
device.ipin the sample request must stay non-EU. The Optable edge derives its privacy jurisdiction from the forwarded IP, and an EU address makes it withhold the ID5 signature.