Many years Selenium is the most popular browser automation tool. However, Selenium protocol still lacks a lot of important features: analyzing and mocking HTTP requests, getting memory consumption and performance metrics, subscribing to application events, retrieving browser security warnings and many more. Fortunately, all this stuff is already supported in the so-called Chrome Developer Tools protocol. There are a lot of talks on how to start using this protocol with client libraries like Puppeteer, but almost nobody tells how to scale this solution. During my talk, I would like to explain how to scale Chrome Developer Tools in Kubernetes cluster and to show some real examples of how you could use this protocol in your tests.

Slides: https://delex-conf.com/talks/2020-talks/master-class-chrome-developer-tools-with-selenoid-moon/

“Selenoid is a powerful implementation of Selenium hub using Docker containers to launch browsers” it describes itself. It’s open source and free. An in particular, it has an enterprise version named “Moon“.
This particular talk is a 45 minutes master class.
Being a mainstream and widely used browser automation tool Selenium protocol lacks many important features: network requests analysis, application performance profiling, accessibility tree access and many more. This is why we are seeing more and more conference talks about so called Chrome Developer Tools protocol where all these features are already present. This protocol is already supported in Selenoid – an extremely efficient Selenium solution running browsers in isolated Docker containers. This talk is a live demonstration of what is Chrome Developer Tools, what you can already do with it and how to use while running parallel Selenium tests in Selenoid.

The most popular browser environments you need to run your tests

The most popular browser environments you need to run your tests