Browser Testing with Docker

Integration tests are an integral part of any modern web application, and regardless of which front-end or server side framework you choose, you'll likely be running Selenium tests. While Selenium tests are easy to write and execute on your local workstation, Works On My Machine™ won't get you past your CI system. Now you're stuck with two bad options, use a SaaS provider and live with slow builds or running your own Selenium Grid and managing a multitude of machines and browser versions. Rock, meet hard place, right? It doesn't have to be that way! In this talk you'll see how easy it is to setup a Selenium Grid with Docker, how easy it is to maintain, and how to extend and grow your Selenium grid to satisfy your team's needs. It's not all roses and sunshine, so you'll see some common issues presented and how to avoid them. Finally, a Selenium Grid you'll want to manage!

[j.d.]

Lot of words, nothing useful about how to set this up

[majidlotfi]

Why don't show us how did you fo the setup, this video is no sense, just waste of time.

[aydinguseynov]

you could just use Saucelabs for cross-browser testing instead of going throw this way.

[padamsandhu]

Safari and Internet Explorer are the browsers which you must test for any continuous integration/deployment.

[diRumahKedua]

Thanks, really great sharing. Can;t wait to build my own docker-selenium grid