This project consists of a Docker image containing a Robot Framework installation.
This installation also contains Firefox, Chrome and the Selenium library for Robot Framework. The test cases and reports should be mounted as volumes.
The versioning of this image follows the one of Robot Framework:
- Major version matches the one of Robot Framework
- Minor and patch versions are specific to this project (allows to update the versions of the other dependencies)
The versions used are:
- Robot Framework 3.2
- Robot Framework DatabaseLibrary 1.2
- Robot Framework Faker 5.0.0
- Robot Framework FTPLibrary 1.9
- Robot Framework IMAPLibrary 2 0.3.6
- Robot Framework Pabot 1.8.0
- Robot Framework Requests 0.7.0
- Robot Framework SeleniumLibrary 4.3.0
- Robot Framework SSHLibrary 3.4.0
- Firefox ESR 78
- Chromium 83.0
As stated by the official GitHub project, starting from version 3.0, Selenium2Library is renamed to SeleniumLibrary and this project exists mainly to help with transitioning. The Selenium2Library 3.0.0 is also the last release and for new releases, please look at the SeleniumLibrary project.
This container can be run using the following command:
docker run \
-v <local path to the reports' folder>:/opt/robotframework/reports:Z \
-v <local path to the test suites' folder>:/opt/robotframework/tests:Z \
ppodgorsek/robot-framework:<version>
Browsers can be easily switched. It is recommended to define ${BROWSER} %{BROWSER} in your Robot variables and to use ${BROWSER} in your test cases. This allows to set the browser in a single place if needed.
When running your tests, simply add -e BROWSER=chrome or -e BROWSER=firefox to the run command.
It is possible to define the settings of the virtual screen in which the browser is run by changing several environment variables:
SCREEN_COLOUR_DEPTH(default: 24)SCREEN_HEIGHT(default: 1080)SCREEN_WIDTH(default: 1920)
It is possible to use different directories to read tests from and to generate reports to. This is useful when using a complex test file structure. To change the defaults, set the following environment variables:
ROBOT_REPORTS_DIR(default: /opt/robotframework/reports)ROBOT_TESTS_DIR(default: /opt/robotframework/tests)
It is possible to parallelise the execution of your test suites. Simply define the ROBOT_THREADS environment variable, for example:
docker run \
-e ROBOT_THREADS=4 \
ppodgorsek/robot-framework:latest
By default, there is no parallelisation.
When using parallelisation, it is possible to pass additional pabot options, such as --testlevelsplit, --argumentfile, --ordering, etc. These can be passed by using the PABOT_OPTIONS environment variable, for example:
docker run \
-e ROBOT_THREADS=4 \
-e PABOT_OPTIONS="--testlevelsplit" \
ppodgorsek/robot-framework:latest
RobotFramework supports many options such as --exclude, --variable, --loglevel, etc. These can be passed by using the ROBOT_OPTIONS environment variable, for example:
docker run \
-e ROBOT_OPTIONS="--loglevel DEBUG" \
ppodgorsek/robot-framework:latest
This project includes the IMAP library which allows Robot Framework to connect to email servers.
A suggestion to automate email testing is to run a Mailcatcher instance in Docker which allows IMAP connections. This will ensure emails are discarded once the tests have been run.
By default, containers are implicitly run using --user=1000:1000, please remember to adjust that command-line setting accordingly, for example:
docker run \
--user=1001:1001 \
ppodgorsek/robot-framework:latest
Remember that that UID/GID should be allowed to access the mounted volumes in order to read the test suites and to write the output.
Additionally, it is possible to rely on user namespaces to further secure the execution. This is well described in the official container documentation:
- Docker: Introduction to User Namespaces in Docker Engine
- Podman: Running rootless Podman as a non-root user
This is a good security practice to make sure containers cannot perform unwanted changes on the host. In that sense, Podman is probably well ahead of Docker by not relying on a root daemon to run its containers.
It is possible to run the project from within a Jenkins pipeline by relying on the shell command line directly:
pipeline {
agent any
stages {
stage('Functional regression tests') {
steps {
sh "docker run --shm-size=1g -e BROWSER=firefox -v $WORKSPACE/robot-tests:/opt/robotframework/tests:Z -v $WORKSPACE/robot-reports:/opt/robotframework/reports:Z ppodgorsek/robot-framework:latest"
}
}
}
}
The pipeline stage can also rely on a Docker agent, as shown in the example below:
pipeline {
agent none
stages {
stage('Functional regression tests') {
agent { docker {
image 'ppodgorsek/robot-framework:latest'
args '--shm-size=1g -u root' }
}
environment {
BROWSER = 'firefox'
ROBOT_TESTS_DIR = "$WORKSPACE/robot-tests"
ROBOT_REPORTS_DIR = "$WORKSPACE/robot-reports"
}
steps {
sh '''
/opt/robotframework/bin/run-tests-in-virtual-screen.sh
'''
}
}
}
}
Not convinced yet? Simple tests have been prepared in the test/ folder, you can run them using the following commands:
# Using Chromium
docker run \
-v `pwd`/reports:/opt/robotframework/reports:Z \
-v `pwd`/test:/opt/robotframework/tests:Z \
-e BROWSER=chrome \
ppodgorsek/robot-framework:latest
# Using Firefox
docker run \
-v `pwd`/reports:/opt/robotframework/reports:Z \
-v `pwd`/test:/opt/robotframework/tests:Z \
-e BROWSER=firefox \
ppodgorsek/robot-framework:latest
For Windows users who use PowerShell, the commands are slightly different:
# Using Chromium
docker run \
-v ${PWD}/reports:/opt/robotframework/reports:Z \
-v ${PWD}/test:/opt/robotframework/tests:Z \
-e BROWSER=chrome \
ppodgorsek/robot-framework:latest
# Using Firefox
docker run \
-v ${PWD}/reports:/opt/robotframework/reports:Z \
-v ${PWD}/test:/opt/robotframework/tests:Z \
-e BROWSER=firefox \
ppodgorsek/robot-framework:latest
Screenshots of the results will be available in the reports/ folder.
Chrome drivers might crash due to the small size of /dev/shm in the docker container:
UnknownError: session deleted because of page crash
This is a known bug of Chromium.
To avoid this error, please change the shm size when starting the container by adding the following parameter: --shm-size=1g (or any other size more suited to your tests)
In case further investigation is required, the logs can be accessed by mounting their folder. Simply add the following parameter to your run command:
- Linux/Mac:
-v `pwd`/logs:/var/log:Z - Windows:
-v ${PWD}/logs:/var/log:Z
Chromium allows to set additional environment properties, which can be useful when debugging:
webdriver.chrome.verboseLogging=true: enables the verbose logging modewebdriver.chrome.logfile=/path/to/chromedriver.log: sets the path to Chromium's log file
When running tests, an unexpected error sometimes occurs:
[Error] Suite contains no tests.
There are two main causes to this:
- Either the test folder is not the right one,
- Or the permissions on the test folder/test files are too restrictive.
As there can sometimes be issues as to where the tests are run from, make sure the correct folder is used by trying the following actions:
- Use a full path to the folder instead of a relative one,
- Replace any
`pwd`or${PWD}by the full path to the folder.
It is also important to check if Robot Framework is allowed to access the resources it needs, i.e.:
- The folder where the tests are located,
- The test files themselves.
As per their official project page, the Robot Framework DatabaseLibrary contains utilities meant for Robot Framework's usage. This can allow you to query your database after an action has been made to verify the results. This is compatible with any Database API Specification 2.0 module.
It is anyway mandatory to extend the container image to install the specific database module relevant to your tests, such as:
- MS SQL:
pip install pymssql - MySQL:
pip install pymysql - Oracle:
pip install py2oracle - PostgreSQL:
pip install pg8000
Have you found an issue? Do you have an idea for an improvement? Feel free to contribute by submitting it on the GitHub project.