electron-cdp-testing

To verify the window.electronAPI preload bridge in an Electron app, connect directly to the live renderer via Chrome DevTools Protocol to probe DOM structure and confirm the bridge is exposed and usable.

The best way to capture UI evidence from an Electron renderer during smoke tests is using Chrome DevTools Protocol to generate reproducible screenshots and DOM summaries that document the current UI state.

Yes, you can use Chrome DevTools Protocol to inspect DOM structure inside an Electron window by establishing a CDP connection, selecting the main page target, and querying the real renderer state directly.

This CDP testing approach works without regular browser debugging tools by connecting directly to the real Electron window via WebSocket, avoiding the drift and brittleness common to standard browser inspection methods.

To run automated UI validation checks against a live Electron window, execute scriptable CDP commands that test window.electronAPI exposure and capture structural evidence for quick local development QA and regression checks.

You should not use Chrome DevTools Protocol for Electron renderer debugging when you need to test backend IPC logic independently of the UI, because this approach specifically targets the live renderer DOM and preload bridge validation.