I built this project to quickly provision a dockerized environment for running UI tests against a dockerized app. It employs a dockerized Selenium Grid which yields a far more cost-effective CI solution compared to purchasing and maintaining dedicated machines.
I've included bash scripts in the bin/
directory as wrappers for the
docker-compose
commands. Hopefully, once you've completed the initial setup,
you won't have to recall any docker commands. 😃
Both RSpec and Watir are automatically provisioned in the testrunner
docker
image. You can easily customize their configurations in spec/spec_helper.rb
.
- a clone of this repo on your machine
- Docker
Here's the default workflow when writing RSpec tests in this project:
bin/build && bin/start && bin/test
- make changes to files inside the spec/ directory
- verify changes with
bin/build && bin/start && bin/test
:sadtrombone:
To make your life easier, first do this:
cp docker-compose.dev.override.yml docker-compose.override.yml
Now any changes you make within this repo on your host file system will
automatically show up in the testrunner
docker container. Here's your new
workflow:
bin/build && bin/start && bin/test
- make changes to files inside the spec/ directory
bin/test
:party:
Some folks have reported file permission issues with this workflow, so YMMV.
By default this project will use a bare-bones Sinatra web app as the system
under test (SUT). If you want to replace that default web app with your own,
open the docker-compose.yml
file, find the web
service configuration, and
replace mycargus/hello_docker_world:master
with your app's docker image label.
For example:
web:
image: my-app-under-test:master
If you're not sure how to create or pull a docker image, I recommend working through the official Docker tutorial located on their website.
Start the Selenium hub, the SUT, and the Selenium browser nodes:
$ bin/start
Execute the tests with Rspec and Watir from inside the testrunner
container:
$ bin/test
When you're done, stop and remove the docker containers:
$ bin/stop
If you're using the default web app provided, then open your browser and go to http://locahost:8080.
If you're using your own web app, make sure to expose a port in your web app's
Dockerfile. For example, if you have EXPOSE 9887
in your web app's Dockerfile,
then you can view it at http://localhost:9887.
Yep! After having started the Selenium hub and nodes (bin/start
), open a
browser and go to http://localhost:4444, then click the 'console' link.
Start the Selenium hub, the app under test, and the Selenium debug browser nodes:
bin/start-debug
View the chrome debug node via VNC (password: secret
):
open vnc://localhost:5900
View the firefox debug node via VNC (password: secret
):
open vnc://localhost:5901
Next execute the tests against the browser nodes and watch them run in the VNC window(s):
bin/test
Again, once you're finished:
bin/stop