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.

1. Selenoid: browsers in containers
by Ivan Krutov

2. About me
Java & Golang developer
Allure Framework contributor
Devops
Big Selenium cluster

3. Big Selenium cluster
5000+ browsers
5 data centers
4000 rps
800 Mbit/s
24/7/365
Linux (desktop)
Windows (IE, Edge)
Android Emulators
iOS Simulators
Real devices

4. Ways to test in browsers

5. #1: test online

6. #2: Selenium Server

7. SelenoidSelenium
#3: Selenoid

8. How Selenium works

9. Linux covers 80% of browsers

10. Let’s use containers!

11. How Selenoid works
Selenoid Container

12. Selenoid without Docker

13. Selenoid applications
Local browser tests development
Creating big Selenium clusters

14. Installation

15. StackOverflow statistics
> 60 000 questions about Selenium

16. Installing Selenium
Manually install Java
Manually download Selenium JAR
Manually download web-driver binaries
Manually unpack web-drivers from archives
Manually install required browsers
Manually type complicated start command

18. Installing Selenoid
Just one short command:
$./cm selenoid start

19. Running tests

20. Selenium window focus problem

21. Selenium browser settings problem

23. Selenoid runs isolated browsers

24. Debugging tests

25. Selenium: grid console and eyes

27. Selenoid: rich UI

28. Selenoid: usage statistics

29. Live Browser Screen

30. Live Selenium Logs

31. Adding new browsers

32. Installing new version is a pain
/usr/bin
FF 45
FF 46

33. Selenium compatibility issues
Chromedriver ???56

34. Computer is cluttered with waste

36. Selenoid: self-contained images

37. Images for all recent browsers
3.6+ 33.0+
12.16
48.0+

38. Custom screen resolution

39. Compatible with other images
https://github.com/SeleniumHQ/docker-selenium
https://github.com/elgalu/docker-selenium
https://github.com/paypal/docker-selion

40. Demo

41. Creating big cluster

42. Selenium Grid

43. Selenium Grid flaws
It is Java increased memory consumption→
Built-in UI consuming resources
No simple way to collect usage statistics & logs
Hard to maintain different browser versions

45. Selenoid: created for big clusters

46. Ultra-fast and lightweight
100% Golang
7 Mb binary
60 Mb RAM

47. Fine-grained resources control
Limit total number of sessions per host
Queues
Limit CPUs per container
Limit RAM per container

48. Tmpfs support

49. Centralized logs support
Selenoid
E
L
K

50. Statistics as JSON
Selenoid
Graphite
InfluxDB
ElasticSearch Grafana

51. Standalone UI

52. Hot configuration reload

53. Ggr for scalability and reliability

54. Some numbers

55. Well documented

56. SelenoidSelenium

57. References
https://github.com/aerokube/selenoid
@aerokube
http://telegram.me/aerokube
http://aerokube.com/
vania-pooh@aerokube.com