Scale up and down the nodes by using docker-compose.
For using it by sharing the host (localhost) network interface see share-host
For requirements check README#requisites
Either clone this repository or download the file docker-compose-tests.yml using wget
wget -nv "https://github.com/raw/elgalu/docker-selenium/latest/docker-compose-tests.yml"
mv -f docker-compose-tests.yml docker-compose.yml
docker-compose -p grid down #ensure is not already running
Start it with docker-compose up
then scale it:
You should replace mock
with your web service under test within the docker-compose-tests.yml file.
export NODES=3 VIDEO=false
docker-compose -p grid up --force-recreate
docker-compose -p grid scale chrome=${NODES} firefox=${NODES}
Wait until the grid starts properly before starting the tests (Optional but recommended)
docker exec grid_hub_1 wait_all_done 30s
for ((i=1; i<=${NODES}; i++)); do
docker-compose -p grid exec -T --index=$i chrome wait_all_done 30s
docker-compose -p grid exec -T --index=$i firefox wait_all_done 30s
done
You can now run your tests by using the --seleniumUrl="http://localhost:4444/wd/hub"
.
However if your web application under test is running in localhost, e.g. --appHost=localhost
or is publicly not accessible
you should instead either dockerize your application as shown in the example adwords_mock within the docker-compose-tests.yml. Its there shown as another service. Another option (if you don't want to dockerize your app yet) is to somehow replace --appHost=localhost
with --appHost=d.host.loc.dev
in the config file of your testing framework. The string d.host.loc.dev
is a place holder inside the docker container that points to the IP of your localhost.
Once your tests are done you can clean up:
docker-compose -p grid down
The down
compose command stops and remove containers, networks, volumes, and images created by up
or scale