Repository navigation
Conversation
2 tasks done
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 preview can execute impression or error URLs even though no live delivery
occurred. This applies the wording proposed in #42 to section 5.4 and adds the
CTV example note. Inspectors must suppress production notifications, return
failures through inspection diagnostics, and distinguish checks that passed
from checks that were skipped or blocked. No payload fields or enums are added.
The supporting fixtures use synthetic VAST documents and loopback notification
traps. The document guard compares normalized HTTP request identities, including
fragment removal, and recognizes companion, non-linear and icon event roles.
Browser assertions preserve the complete notification log and fail on any
notification during an isolated case, including unexpected paths or methods.
Validation: 41 document/URL cases, 27 browser cases and 10 notification-assertion
cases pass. The original audit reproductions now produce zero event requests.
An integration canary deliberately sends one unexpected event from the test
driver; exactly that isolated case fails, and its receipt retains the event.
Five deliberate creative/assertion regressions are detected. Existing appendix
checks and YAML parsing also pass.
The Python and notification-assertion tests are wired into CI. The browser
demonstration is a documented local command using Node.js 22 and Chrome/Chromium;
the tested browser was Chrome 155.0.8059.80. It is supporting synthetic evidence,
not a production sandbox, a VAST player or a readiness service. Media playback,
real verification SDKs and seller approval are not established by these tests.
Refs #42. Related: #32. Reproduction and scope are documented in
docs/creative-inspection-fixtures.md.Member of the IAB Tech Lab Agentic Taskforce, commenting in a personal capacity.