Rolling main documentation

Built from commit 1810c763add220dd34fd5faaffe2c69aab1d556f. Content may describe unreleased behavior.

Auction testing

Use controlled upstream fixtures for auction tests. Do not point local smoke tests at production bidder endpoints.

Validate the configuration first

The CLI compiles the complete target-independent AuctionPlan, including provider profiles, bidder routes, extension bounds, notification settings, and mediator selection:

ts config validate --strict

For a local Fastly run, write the validated envelope into Viceroy state before starting the adapter:

ts config push --adapter fastly --local
fastly compute serve

fastly compute serve alone is insufficient: the checked-in config store is empty, and non-health requests fail until a valid app-config envelope is available.

Exercise POST /auction

Configure each provider endpoint to a controlled fixture, then send a Prebid-compatible request:

curl --fail-with-body \
  --header 'content-type: application/json' \
  --request POST \
  --data '{"adUnits":[{"code":"header-banner","mediaTypes":{"banner":{"sizes":[[728,90]]}}}]}' \
  http://localhost:7676/auction

Check the response and logs for these invariants:

• a disabled auction returns a no-bid response without provider dispatch;
• routing = "explicit" sends a slot only to its mapped provider;
• routing = "all_eligible" sends eligible banner slots without leaking another provider's bidder parameters;
• provider-local failures do not fabricate bids;
• with no mediator, the orchestrator selects the highest valid bid per slot;
• with mediator = "adserver_mock", the configured mediator owns final selection; and
• APS winners use ext.trusted_server.renderer rather than raw adm.

Run automated coverage

The shared auction tests run through the target-specific aliases:

cargo test-fastly auction
cargo test-axum auction
cargo test-cloudflare auction
cargo test-spin auction
cargo test --manifest-path crates/trusted-server-integration-tests/Cargo.toml --test parity auction

Fastly and Axum support multi-provider fan-out. Cloudflare and Spin reject an enabled plan with more than one provider at startup, so their negative tests are part of the contract rather than skipped coverage.

See Auction orchestration for configuration and response details.

Absolute deadline regressions

Core tests cover split dispatch/collection and synchronous execution, pending provider attribution, preserved on-time bids, late collection after an origin wait, and exhausted-budget mediation. Axum loopback tests separately delay headers and trickle bodies, and verify outstanding task cancellation. Worker adapter tests use controlled futures and timers. CI also runs the actual worker HTTP clients under local workerd and Spin 4.1, covering eager dispatch, buffered bids after a slow origin, delayed headers, and trickling bodies. Run node scripts/test-worker-auction-deadlines.mjs --help for the same local fixtures. Fastly also has Viceroy network fixtures for stalled headers, trickling bodies, bodyless responses, and competing bidders. Its local origin harness builds the adapter test binary itself:

node crates/trusted-server-adapter-fastly/tests/deadline-origin.mjs "$(command -v viceroy)"

The harness binds a local ephemeral port and runs the five network tests excluded from the standard suite; CI runs the same command. To reuse a prebuilt test artifact, pass its .wasm path as a second argument.