Devtools Proxy

A "sort-of-a-proxy" to poke Chrome DevTools --remote-debugging-port with HTTP calls

See DEVELOPMENT.md for development & build instructions

Explanation

What is for?

• To enable drill-session-id and drill-test-name propagation (used both by Java and & JS autotest agents)
• To enable JavaScript coverage collection from Selenium tests

Why? (why not make calls to Chrome DevTools from tests code)

Yes, it is a viable solution, but it would force us to implement these calls each time we want to support new language/platform supported by Selenium.

And how is that different?

This is a standalone component that accepts HTTP calls and sends CDP commands (via WebSocket) to DevTools. Thus, we only to implement a HTTP calls in test lifecycle hooks.

Environment variables / launch options

• FETCH_INTERCEPTED_RESOURCE_TYPES - comma-separated list of Network.ResourceType to intercept via Fetch.enable. Utilized in /intercept API. See implementation for up-to-date list of intercepted resources (initially - Document, XHR, Fetch)