Adblock Labs — Browser Blocking Test Suite

Internal test pages for verifying Adblock end-to-end blocking behaviour in Chrome.

Phase 1 pages

third-party-script — loads googletagmanager.com/gtag/js. Expected: blocked.
tracking-pixel — loads a 1×1 from google-analytics.com/collect. Expected: blocked.
allow-list-control — fetches a benign first-party asset. Expected: NOT blocked (over-blocking canary).

Phase 2 pages — network blocking surfaces

third-party-iframe — embeds a doubleclick.net ad iframe (iframe navigation block). Expected: blocked.
third-party-css — loads a stylesheet from googletagmanager.com (CSS request block). Expected: blocked.
beacon-tracker — navigator.sendBeacon POST to google-analytics.com/collect (POST beacon path). Expected: blocked.
xhr-fetch-tracker — explicit fetch with mode: 'cors' to google-analytics.com/collect (XHR/fetch path). Expected: blocked.
websocket-tracker — WebSocket upgrade to stats.g.doubleclick.net (WS upgrade block). Expected: blocked.
webworker-tracker — Worker sourced from googletagmanager.com (worker-script fetch). Expected: blocked.
video-tracker — <video> source from googleads.g.doubleclick.net (video-element URL block). Expected: blocked.
third-party-preconnect — preconnect/dns-prefetch to doubleclick.net with verification fetch (preconnect/DNS suppression). Expected: blocked.

Note: these pages are consumed by BlockingRecorder in Adblock.ReleaseTests. They report verdicts via window.__adblockTestResult and are evaluated against CDP Network.loadingFailed events. Manual visits are fine for sanity checks; meaningful pass/fail comes from the automated runner. See Linear ENG-682.