There seem to be three predominant setups for running automated tests.
- The company invested in a selenium grid that is always available and the nightly tests run against them.
- The CI will build a test runner, selenium grid on demand, run the tests and then wind down after the job is finished
- Have the test runner, tests, browser driver and browser in an image, build the container on demand, run the tests and then wind down (not much popular but the fastest in my opinion)
Till recently I was a fan of the third option. I used to run ruby based selenium tests in a container built from an image containing ruby, chrome driver and chrome. The tests are stable, runs fast. These used to run nightly on Jenkins.
I am curious to know what do the industry follow and what is the best suggested approach is