Hello, Habr! We at Wrike are testing new formats of technical events and invite everyone to watch the video of our first online meetup in English. DevOps infrastructure for testing web applications, containers, Selenium and its alternatives.
The spread of the coronavirus and bans on all large offline events in European countries brought changes, so the planned Wrike Prague offline meeting of testers and DevOps has moved to YouTube.
Attention, presentations will be in English.
1. Mikhail Levin, Wrike – Selenium — road to Kubernetes
Once upon a time Selenium lived and grew. It was probably the best thing that happened for QA automation in the last two decades, and yeah, that wasn’t easy in many ways including infrastructure and stability.
With long experience in Selenium grid infrastructure and alternatives, I want to walk you through some issues and limitations of different Selenium infrastructures up to our brand new lightweight solution.
2. Vitaliy Markov, Wrike – Callisto: how we learned to stop worrying and love Selenium
Meet Callisto — our lightweight and open-source Kubernetes-native solution for building Selenium infrastructure. We run tens of thousands of Selenium tests in one hour and survive hundreds of daily Selenium test runs with it. We want to share our reasons, the solution itself, and the technical details learned along the way. Our experience might come in handy whether you run that many Selenium tests or you just have some session-based work to run in Kubernetes across multiple threads.
3. Ivan Krutov, Aerokube – Chrome Developer Tools Protocol: running and scaling in Kubernetes
For many years, Selenium has been the most popular browser automation tool. However, the Selenium protocol still lacks many 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 of this is already supported in the so-called Chrome Developer Tools protocol. There are many discussions on how to start using this protocol with client libraries like Puppeteer, but almost nobody explains how to scale this solution. During my talk, I will explain how to scale Chrome Developer Tools in a Kubernetes cluster and show some real examples of how you can use this protocol in your tests.
Source: habr.com
