Talk Details

Parallel frontend test execution using Selenium and Docker

Development Practices

Nowadays, the main problem regarding frontend test execution is the time spent to cover the necessary scenarios to get the proper quality feedback. It's no wonder that we are focusing more on the earlier test stages like unit and integration. But frontend tests are also important, so how to make them faster?

I could reduce 2 days of manual tests to 35min of sequential tests to 6min parallel tests for the same test suite! So you also can!

We can achieve it by mixing a parallel test execution strategy together with a container approach, auto-scaling its usage of it per request. Do you think it's complicated? Believe me, it's not!

The trick is done by combining three different things:

  1. a good code design, preparing it for a test parallelization using the Factory Pattern to create different driver instances based on the test requests
  2. the usage of the built-in parallel strategy from your preferred test library
  3. the usage of the Selenium 4 Grid containers, creating an orchestration to be able to auto-scale the different containers with web browsers

We will combine it all together, learning how to create the necessary code with the infrastructure to speed up the frontend test execution.

Elias Nogueira


Elias is a Principal Engineer in Test who helps software engineers to develop their quality mindset and deliver bug-free software. His specialization is in Quality Engineering for backend, frontend, and mobile technologies. He's a writer, blogger, and loves to help the community by running meetups and sharing knowledge by giving presentations around the world.