Unleash the power of Chrome Developer Tools with Selenoid

Being a mainstream and widely used browse automation tool Selenium protocol however still lacks many important features: network requests analysis, application performance profiling, accessibility tree access and many more. Hopefully all of them are already supported in so called Chrome Developer Tools protocol and which is more important this protocol is already supported in Selenoid - an extremely efficient Selenium solution running browsers in isolated Docker containers. In this talk I will tell you what is Chrome Developer Tools protocol, how it works, what are its powerful features and how to use the most important features of this protocol in different browsers being run remotely and in parallel.

 
 

Outline/Structure of the Talk

1) About myself

2) Which features are missing in standard Selenium

3) What is Chrome Developer Tools protocol, how it works

4) Chrome Developer Tools protocol support in Selenoid

5) How to start using this protocol in your tests (most probably example code will be using Puppeteer)

Learning Outcome

1) What is Chrome Developer Tools protocol

2) What are the most important features it provides

3) How to use Chrome Developer Tools with Selenoid and how integrate developer tools to your tests

Target Audience

Everybody interested in knowing what are the latest emerging approaches of making automated testing more efficient.

schedule Submitted 3 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Anand Bagmar
    By Anand Bagmar  ~  2 months ago
    reply Reply

    Hi Ivan,

    One aspect that I find missing in this proposal is the "Why do I need Chrome Dev Tools as part of my Selenium Tests".

    Regards,

    Anand

    • Ivan Krutov
      By Ivan Krutov  ~  2 months ago
      reply Reply

      I'm expecting to explain this in "Which features are missing in standard Selenium" section. Because Chrome Devtools protocol is mainly needed as an extension of basic Selenium features.


  • Liked Roman Orlov
    keyboard_arrow_down

    Roman Orlov - 5 reasons to run your Selenium tests in Kubernetes... and how to do that

    Roman Orlov
    Roman Orlov
    DevOps
    Aerokube
    schedule 3 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    During the last years we in Aerokube team created and demonstrated truly efficient Selenium tools: Selenoid and Ggr. With two small daemons you can easily organize a reliable Selenium cluster where each browser will be running in separate Docker container.

    In this talk I would like to address another important question - Selenium cluster resources consumption. I will explain step by step why running browsers in Kubernetes cluster can dramatically decrease your Selenium cluster cost. You will see how to consume times less computing resources and still have the same powerful Selenium features like video recording, debugging running tests, creating browser sessions for manual testing and so on.

    I will show how to install, manage and scale Selenium cluster in Kubernetes using Aerokube Moon solution and compare resulting cluster cost to other popular solutions.