TA #3 — Evolution of test infrastructure

[TA] — Test Automation article series

Selenium Server and Grid

Pros

• open-source
• aka standard
• large community

Cons

• Manually install (Java, Selenium JAR, Web driver binaries, required browsers)
• when running in parallel can lost windows focus
• can be a lot of pitfalls during running and maintaining
• not user-friendly UI and can’t see tests in runtime over VNC Viewer

Selenium Server and Grid managed by Docker

Pros

• open-source
• allow run every test from a fresh state using Docker container
• selenium community support it as well and provider ready Docker images

Cons

• Docker skillset (require a bit time to config it greate)

Selenoid

Pros

• open-source
• it represents already configured Dockerized Selenium Server and Grid with easily configurable software
• provide user-friendly monitoring UI
• No need to know Docker
• Local running
• Creating big Selenium Clusters
• Sync web driver version with the browser
• can customize screen resolution

Cloud-based infrastructure (Sauce Labs, BrowserStack, TestingBot)

Pros

• Works out of the box, all infrastructures are in that services
• All configurations come from web driver capabilities of our framework
• provide user-friendly UI monitoring
• no need any local set up
• can customize screen resolution

Cons

Expensive $$$