Wrike TechClub: Delivery infrastructure – processes and tools (DevOps+QAA). Π”ΠΎΠΊΠ»Π°Π΄Ρ‹ Π½Π° английском

ΠŸΡ€ΠΈΠ²Π΅Ρ‚, Π₯Π°Π±Ρ€! ΠœΡ‹ Π² Wrike тСстируСм Π½ΠΎΠ²Ρ‹Π΅ Ρ„ΠΎΡ€ΠΌΠ°Ρ‚Ρ‹ тСхничСских мСроприятий ΠΈ ΠΏΡ€ΠΈΠ³Π»Π°ΡˆΠ°Π΅ΠΌ всСх ΠΏΠΎΡΠΌΠΎΡ‚Ρ€Π΅Ρ‚ΡŒ Π²ΠΈΠ΄Π΅ΠΎ нашСго ΠΏΠ΅Ρ€Π²ΠΎΠ³ΠΎ ΠΎΠ½Π»Π°ΠΉΠ½-ΠΌΠΈΡ‚Π°ΠΏΠ° Π½Π° английском. ΠŸΠΎΠ³ΠΎΠ²ΠΎΡ€ΠΈΠ»ΠΈ ΠΏΡ€ΠΎ DevOps инфраструктуру для тСстирования Π²Π΅Π±-ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠΉ, ΠΊΡƒΠ±Ρ‹, Selenium ΠΈ Π΅Π³ΠΎ Π°Π»ΡŒΡ‚Π΅Ρ€Π½Π°Ρ‚ΠΈΠ²Ρ‹.

Wrike TechClub: Delivery infrastructure – processes and tools (DevOps+QAA). Π”ΠΎΠΊΠ»Π°Π΄Ρ‹ Π½Π° английском

Π˜ΡΡ‚ΠΎΡ€ΠΈΡ с распространСниСм коронавируса ΠΈ Π±Π°Π½Ρ‹ всСх массовых ΠΎΡ„Π»Π°ΠΉΠ½-мСроприятий Π½Π° Ρ‚Π΅Ρ€Ρ€ΠΈΡ‚ΠΎΡ€ΠΈΠΈ СвропСйских государств внСсли свои ΠΊΠΎΡ€Ρ€Π΅ΠΊΡ‚ΠΈΠ²Ρ‹, поэтому запланированная Wrike Prague ΠΎΡ„Ρ„Π»Π°ΠΉΠ½ встрСча тСстировщиков ΠΈ Π΄Π΅Π²ΠΎΠΏΠΎΠ² ΠΏΠ΅Ρ€Π΅Ρ‚Π΅ΠΊΠ»Π° Π² ΡŽΡ‚ΡŒΡŽΠ±.

Π’Π½ΠΈΠΌΠ°Π½ΠΈΠ΅, Π΄ΠΎΠΊΠ»Π°Π΄Ρ‹ Π½Π° английском языкС.

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 of Selenium infrastructure. We run 10th 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 technical details learned on the way. Our experience might come in handy whether you run that much of selenium tests or you just have some session based work to be run in k8s in many threads.

3. Ivan Krutov, Aerokube – Chrome Developer Tools Protocol: running and scaling in Kubernetes

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.



Π˜ΡΡ‚ΠΎΡ‡Π½ΠΈΠΊ: habr.com