Babu Narayanan will be presenting the following session
filter_list help_outline
  • Gopinath Jayakumar
    keyboard_arrow_down

    Gopinath Jayakumar / Babu Narayanan Manickam - Expanding boundaries of WebDriver with DevTools Integration

    45 Mins
    Demonstration
    Beginner

    Problem Statement

    Though Selenium taking most of the stake in the UI test automation tool market comfortably, there were always challenges that were for selenium test automation engineers are handicapped with especially when dealing with modern JS technologies. For example,

    • dealing with DOM elements to solve the stale / loading / non-interactable elements,
    • handling full screenshots to know how the elements at the left, bottom, etc,
    • measuring the performance of request and response resources at different speeds,
    • monitoring the memory of the pages, controls, etc,
    • attaching to an existing browser for debugging the failed scripts and many more.

    These problems were largely resolved with the integration of selenium with devtool protocols. And that makes the selenium engineer's life merrier than before.

    Why this proposal can be different from others?

    1. Our solution can be executed as independent with chrome dev tools or with selenium. That gives the power back to the automation engineer to choose what and how to debug/run their tests.
    2. We used this solution for one of our largest enterprise customers and moved this solution to public repository this week (for this conference and beyond). With that said, we tested reasonably with more than 10,000+ test scripts and more than 1M tests.
    3. The present solution is completely (100%) packed with all Chrome Dev Tools API in Java and with that said, any Java Selenium automation engineer can bind in minutes for their existing code base with no additional dependencies.
    4. Finally, we love to present at the local home to start our selenium conference campaign. Where else?

    Solution:

    The present proposal largely connected with Chrome and Selenium in Java language. However, there is no limitation to expand the boundaries for other language bindings and browsers.

    Google Chrome, the most picked browser for browsing, which makes it the primary concentration for developers and testers. DevTools is one such boon for developers, testers especially the new aged test automation engineers. With that said, we built the following design pattern to allow chrome dev tools API to marry Selenium using debugger address / remote targets.

    Selenium Devtools

1. What got you started/interested in Testing?

Kick starting my IT career in development in late 90s with ColdFusion followed by J2EE, the unit testing in early 2000 were limited and constrained. Considering the number of defects leaked to test and production forced me to build automation test suite those days and that enabled me into serious testing and test automation profession. 

2. What has been your best moment/highlight working with Selenium?

It is the power of Selenium Webdriver API. The best moment so far is all about customizing and enhancing the selenium webdriver API for our product usage like auto-enabled retries on selector failures, timeout challenges etc.

3. What do you think is the biggest challenge faced by Software Testers today?

The biggest challenge for most of the software testers are mindset block towards enabling test automation at their own work. Many of them either believe it is difficult to code until they start coding themselves and possibly the other could the organization culture that blocks them. 

4. What is your advice to testers, who are new to automation?

My biggest advise to newbies are start automation with clean coding practices and it is not about how many tests you are automating and it is all about the quality value proposition that you bring to your product / application through automation. 

5. Tell us about the session(s) you will be presenting at the conference and why did you choose those topics?

Before Selenium 4, the webdriver is limited to conversation with browser DOM and hence there were limitations. Same time, the power of Developer Tools API with integration of Selenium WebDriver API can provide the stronger UI automation capabilities in all browser domains from Page, DOM to Memory. We felt that this topic is the most wanted in today's world considering the growing demand for UI automation and devops ecosystem.

6. What are some of the key takeaways from your session(s)?

If you are an automation engineer, then you will have many takeaways including the solutions of several struggles you may have with UI automation through Selenium Webdriver like

  • How to take full screenshots and that can help to expose defects or confirm correctness?
  • Way to perform auto authentication on your application through network request
  • How to enable geo location based test automation
help