QA Fest 2018. Иван Крутов. 1001 причина использовать Ggr в своем кластере Selenium

•

0 likes•456 views

Современная разработка невозможна без эффективных инструментов. Тестирование и, в особенности, автоматическое тестирование в браузерах не исключение. С ростом команды вам требуется все больше и больше параллельно запускаемых браузеров. Всем известный Selenium server и архитектура Selenium Grid начинает работать медленно даже при нескольких десятках работающих браузеров. Ggr - это легковесное решение, отлично работающее даже в очень больших кластерах, состоящих из тысяч параллельно работающих браузерных сессий. Этот доклад подробно рассматривает Ggr - эффективный балансировщик нагрузки для Selenium, незаменимый в случае, если вам нужно запускать десятки с сотни параллельных сессий. Я начну с основ балансировки нагрузки в Selenium и покажу все основные возможности Ggr. Вы увидите как легко посмотреть на любую работающую сессию в реальном времени или скачивать видео прошедших тестов для любой из сессий, выполняющихся на сотнях Selenium хостов.

Education

1001 reasons to use Ggr in your
Selenium installation
by Ivan Krutov

About me
Java & Golang developer
Selenoid core maintainer
Devops
Big Selenium cluster

Selenium clusters
Typical Selenium Grid
50 browsers
10000 sessions / day
1 data center
5 rps
500 Kbit/s
Sometimes down
My cluster
5000+ browsers
2.5M sessions / day
5 data centers
4000 rps
2 Gbit/s
24/7/365

Why
Growing number of desired browser sessions
Growing number of teams
Need to use different platforms

Browser consumption control
x 100
x 50
x 10someuser

Client-side load balancing
Fault-tolerant
Scalable
No access control
Not standard Selenium

GoGridRouter (aka Ggr)
100% Golang
6 Mb binary
400 rps 200 Mb RAM→

How to run your tests
Standard Selenium server:
http://example.com:4444/wd/hub
GridRouter:
http://user:password@example.com:4444/wd/hub

Multiple Datacenter Problem
Ggr1
Ggr2
Host with browsers
New session
Open page
?

Original session ID:
e0dfdda0-1786-4e8f-987b-29a61f5c165e
md5(‘http://example.com:4444’):
798744d2b7036ba36c4ea285272bcd48
Extended session ID:
798744d2b7036ba36c4ea285272bcd48e0dfdda0-
1786-4e8f-987b-29a61f5c165e
Session ID magic

Graphical User Interface
Selenoid
/status
Selenoid UI

Ggr UI
Ggr UI
/status
Selenoid UI
Selenoid 1
Selenoid N
Selenoid 2
...
/status

Proxying Logs and Videos
Selenoid 1
Selenoid N
Selenoid 2
...
Ggr
/logs/session-id.log
/video/session-id.mp4
long-session-id

Ggr is Selenium Future
Selenium Grid Ggr

References
@aerokube
https://t.me/aerokube
https://aerokube.com/
vania-pooh@aerokube.com
https://github.com/aerokube/selenoid
https://github.com/aerokube/ggr
https://github.com/aerokube/ggr-ui

This document discusses Ggr, a server-side load balancer for large Selenium clusters. Ggr provides client-side load balancing, fault tolerance across multiple data centers, scalability, access control, and browser consumption control for Selenium grids with thousands of browsers. It uses a standard Selenium API and supports modifying clusters without downtime by reloading its configuration via SIGHUP. The document demonstrates how to run tests through Ggr, handle session IDs across data centers, scale the cluster, and view status and logs through Ggr's graphical user interface. It argues that Ggr represents the future of Selenium grids for large testing needs.

Chrome Developer Tools Protocol: Scaling and Running in Kubernetes cluster

Ivan Krutov

This document discusses using the Chrome Developer Tools Protocol (CDP) to remotely control and automate Chrome browsers running in a large Kubernetes cluster for browser testing. It describes how CDP allows direct manipulation of page elements, network requests, and more compared to traditional Selenium automation. The author explains how running CDP-enabled Chrome containers in Kubernetes provides a scalable and cost-efficient solution for browser testing and automation. Key points covered include using CDP proxies, services, and deployments in Kubernetes as well as optimizations for hardware costs and efficient resource usage.

Windows Browsers: How to Run them in Docker containers

Ivan Krutov

Chrome Developer Tools with Selenoid

Ivan Krutov

The document discusses using Chrome Developer Tools with Selenoid to enable direct DOM tree and CSS style manipulation, network activity tracking, accessibility tree inspection, and event subscription for large Selenium clusters. It introduces the Chrome Developer Tools Protocol (CDP) which allows communication over JSON and websockets, and provides an example of using CDP with Selenoid to remotely control browsers for testing.

Grid Router – scalable and fault tolerant solution for Selenium grid

Mikhail Levin

Selenium-Grid-Extras

Shawn McCarthy

Grid Extras is a tool that enhances Selenium Grid functionality by automatically updating web drivers, restarting nodes after a set number of tests, and providing centralized node configuration, video recordings of test runs, OS screenshots, and more advanced capabilities than a standard Grid installation. It aims to improve the Selenium Grid testing process through features like auto-updating browser versions, handling protected content modes in Internet Explorer, and allowing contributions from the open source community. The presenter is a contributor to Grid Extras, helps users on IRC and forums, and works as an SDET at GoDaddy to promote test automation.

Meet the Selenium Grid

Alexey Nikolaenko

Server-Side JavaScript with Nashorn

Daniel Woods

Server-Side JavaScript with Nashorn Nashorn is a JavaScript engine that runs on the Java Virtual Machine (JVM), allowing for server-side JavaScript. It provides full ECMAScript 5.1 compliance and interoperability with Java libraries and frameworks. Nashorn performance is improving with recent Java updates and will soon reach near-native levels, making the JVM a platform for high-performance dynamic languages like JavaScript on the server-side.

This document discusses scaling Android tests using Selenoid. It notes that over 50% of internet traffic is from mobile, with about 75% from Android devices. Testing Android applications is complicated due to device variations. Using real devices is difficult due to low battery, connectivity issues, and limited lifetime. The document outlines how Selenium works with desktop browsers and how it can work with Android using the Android Debug Bridge, emulators, and frameworks like UI Automator and Appium. It proposes using Selenoid with Docker containers running Android images to provide scalable, isolated Android environments for testing. This approach allows tests to start in 5-10 seconds using memory snapshots and can scale to thousands of tests per day across multiple data centers.

Selenium in Kubernetes: lessons learned

Ivan Krutov

Oreo, Nougat, Marshmallow and Lollipop: Efficient Android testing in 2019.

Ivan Krutov

This document discusses efficient Android testing in 2019 using tools like Selenoid and Appium. It describes setting up a large Selenium cluster with over 5000 browsers and 2.5 million test sessions per day across 5 data centers for testing Android applications and mobile web. Custom Android images are created using Selenoid to allow quick boot times and testing directly on emulated Android environments without needing real devices.

Selenoid: browsers in containers

Ivan Krutov

Selenoid is a tool for running Selenium tests in isolated browser containers. It allows running thousands of browsers across multiple data centers with high throughput. Selenoid containers include pre-installed browser versions and drivers so tests can be run with a single command. This simplifies setup and allows easy maintenance of browser versions and compatibility. Selenoid is lightweight, scalable, and provides centralized logging and usage statistics which makes it suitable for large test clusters running 24/7.

QA Fest 2017. Иван Крутов. Selenoid: запускаем Selenium тесты в Docker контей...

QA Fest 2018. Иван Крутов. 1001 причина использовать Ggr в своем кластере Selenium

Recommended

Recommended

More Related Content

Similar to QA Fest 2018. Иван Крутов. 1001 причина использовать Ggr в своем кластере Selenium

Similar to QA Fest 2018. Иван Крутов. 1001 причина использовать Ggr в своем кластере Selenium (20)

More from QAFest

More from QAFest (20)

Recently uploaded

Recently uploaded (20)

QA Fest 2018. Иван Крутов. 1001 причина использовать Ggr в своем кластере Selenium