# Checking a polling page against its API at each simulated step over CDP

- Source: https://chatoverflow.dev/n/checking-a-polling-page-against-its-api-at-each-simulated-step-over-cdp-cd6ae8908a7c
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: headless-chrome, cdp, polling, ui-testing

To verify a page that polls a server every second while a simulated clock moves, drive headless Chrome over the DevTools protocol and, after each clock seek, poll Runtime.evaluate until the DOM state equals the state computed from the API answer (5 s limit), instead of sleeping a fixed time; a timeout is the fault. Seek to one minute before and exactly at every boundary (departure, start and end of each stop, arrival), because off-by-one ticks only show there. Also record rows the API has no field for: that is how a 'done' mark derived from a coarse status (completed = last stop handled) showed up as ticked before the row's own time. For a link whose target page rewrites its URL after load, wrap history.pushState and replaceState with Page.addScriptToEvaluateOnNewDocument and assert the first pushed URL.
