Robottelo is a test suite which exercises The Foreman. All tests are automated, suited for use in a continuous integration environment, and data driven. There are three types of tests:


The following is only a brief setup guide for Robottelo. The section on Running the Tests provides a more comprehensive guide to using Robottelo.

Robottelo requires SSH access to the Satellite 6 system under test, and this SSH access is implemented by Paramiko. Install the headers for the following to ensure that Paramiko’s dependencies build correctly:

  • OpenSSL

  • Python development headers

  • libffi

Recommendation: Create a virtual python environment for the following setup.

Create virtual environment for python 3.x:: $ python3 -m venv <venv_name> To activate virtual environment: $ source <venv_name>/bin/activate To end the session: $ deactivate

On Fedora, you can install these with the following command:

For python3.x:

dnf install -y gcc git libffi-devel openssl-devel python38-devel redhat-rpm-config libcurl-devel libxml2-devel

On Red Hat Enterprise Linux 7, you can install these with the following command:

yum install -y gcc git libffi-devel openssl-devel python38-devel redhat-rpm-config libcurl-devel libxml2-devel

For more information, see Paramiko: Installing.

Get the source code and install dependencies:

$ git clone git://
$ export PYCURL_SSL_LIBRARY=<ssl library>
$ pip install -r requirements.txt

Notes: * To determine ssl library, check

That’s it! You can now go ahead and start testing The Foreman. However, there are a few other things you may wish to do before continuing:

1. You may want to install development tools (such as gcc) for your OS. If running Fedora or Red Hat Enterprise Linux, execute yum groupinstall "Development Tools". Make sure to use dnf instead of yum if dnf is available on your system. 2. You may wish to install the optional dependencies listed in requirements-optional.txt. (Use pip, as shown above.) They are required for tasks like working with certificates, running the internal robottelo test suite and checking code quality with pre-commit.

Robottelo on Docker

Robottelo is also available on dockerhub.:

$ docker pull satelliteqe/robottelo

It also can be built locally using the Dockerfile, in the main directory.:

$ docker build -t robottelo .

In order to run tests, you will need to mount your file.:

$ docker run -v {path to robottelo dir}/ satelliteqe/robottelo <test command>

You can also mount the entire robottelo directory to include the properties file and any new tests you have written.:

$ docker run -it -v {path to robottelo dir}:/robottelo satelliteqe/robottelo /bin/bash


  • CLI tests run easiest if you include the root credentials in server.yaml

  • UI tests should be configured to run through your SauceLabs account.

Running the Tests

Before running any tests, you must create a configuration file:

$ cp ./
$ vi
$ cd conf
$ cp broker.yaml.template ./broker.yaml
$ vi broker.yaml
$ cp robottelo.yaml.template ./robottelo.yaml
$ vi robottelo.yaml
$ cp server.yaml.template ./server.yaml
$ vi server.yaml

That done, you can run tests using make:

$ make test-robottelo
$ make test-docstrings
$ make test-foreman-api
$ make test-foreman-cli
$ make test-foreman-ui
$ make test-foreman-smoke

Robottelo provides two test suites, one for testing Robottelo itself and another for testing Foreman/Satellite 6. Robottelo’s tests are under the tests/robottelo directory and the Foreman/Satellite 6 tests are under the tests/foreman directory.

If you want to run tests without the aid of make, you can do that with either pytest , unittest or nose. Just specify the path for the test suite you want to run:

$ pytest tests/robottelo
$ pytest tests/foreman
$ python -m unittest discover -s tests/robottelo -t .
$ python -m unittest discover -s tests/foreman -t .
$ nosetests tests/robottelo
$ nosetests tests/foreman

The following sections discuss, in detail, how to update the configuration file and run tests directly.

Initial Configuration

To configure Robottelo, multiple template yaml files are present to execute different test cases in Robottelo. 1. server.yaml : Populate server.yaml with ssh credentials and ssh key path. Then, edit the configuration file so that at least the following attributes are set:


Note that you only need to configure the SSH key if you want to run CLI tests. There are other settings to configure what web browser to use for UI tests and even configuration to run the automation using SauceLabs. For more information about what web browsers you can use, check Selenium’s WebDriver documentation.

Using environment variables

Each of the sections in the file can be mapped to an environment variable prefixed with ROBOTTELO_ so for example if you want to override the server.hostname without changing the properties file you can do:

$ export

The envars follows the format ROBOTTELO_{SECTION}_{VALUE} all uppercase, more examples:

$ export ROBOTTELO_SERVER_SSH_KEY=path/to/your/key
$ export ROBOTTELO_BUGZILLA_API_KEY=sdfsdg654g8df4gdf6g4df8g468dfg

Running the UI Tests in headless mode

You can run browser for UI tests in headless mode by setting browser option in file. Currently it is supported only for chrome


Testing With Pytest

To run all tests:

$ pytest

It is possible to run a specific subset of tests:

$ pytest
$ pytest
$ pytest

To get more verbose output, or run multiple tests:

$ pytest tests/ -v
$ pytest tests/robottelo/ \


To test The Foreman’s API, CLI or UI, use the following commands respectively:

$ pytest tests/foreman/api/
$ pytest tests/foreman/cli/
$ pytest tests/foreman/ui/

To collect from three directories in one run:

$ pytest tests/foreman/{cli,api,ui}/

To search in testcase names, in this case it will run just negative tests:

$ pytest tests/foreman/cli/ -k negative

To run tests in several threads, in this case 4:

$ pytest tests/foreman/cli/ -n 4

For more information about Python’s pytest module, read the documentation.

Testing With Unittest

To run all tests:

$ python -m unittest discover \

–start-directory tests/ –top-level-directory .

It is possible to run a specific subset of tests:

$ python -m unittest tests.robottelo.test_decorators
$ python -m unittest tests.robottelo.test_decorators.DataDecoratorTestCase
$ python -m unittest tests.robottelo.test_decorators.DataDecoratorTestCase.test_data_decorator_smoke

To get more verbose output, or run multiple tests:

$ python -m unittest discover -s tests/ -t . -v
$ python -m unittest \

tests.robottelo.test_decorators tests.robottelo.test_cli

To test The Foreman’s API, CLI or UI, use the following commands respectively:

$ python -m unittest discover -s tests/foreman/api/
$ python -m unittest discover -s tests/foreman/cli/
$ python -m unittest discover -s tests/foreman/ui/

For more information about Python’s unittest module, read the documentation.

Testing With Nose

You must have nose installed to execute the nosetests command.

To run all tests:

$ nosetests

It is possible to run a specific subset of tests:

$ nosetests tests.robottelo.test_decorators
$ nosetests tests.robottelo.test_decorators:DataDecoratorTestCase
$ nosetests tests.robottelo.test_decorators:DataDecoratorTestCase.test_data_decorator_smoke

To get more verbose output, or run multiple tests:

$ nosetests -v
$ nosetests tests.robottelo.test_decorators tests.robottelo.test_cli

To test The Foreman’s API, CLI or UI, use the following commands respectively:

$ nosetests tests.foreman.api
$ nosetests tests.foreman.cli
$ nosetests tests.foreman.ui

Many of the existing tests use subTest to allow for a more data-driven methodology. In order to run a specific test you need to override the way nosetests discovers test names. For instance, if you wanted to run only the test_positive_create_1 data-driven tests for the foreman.cli.test_org module:

$ nosetests -m test_positive_create_1 tests.foreman.cli.test_org

Running UI Tests On a Docker Browser

It is possible to run UI tests within a docker container. To do this:

  • Install docker. It is provided by the docker package on Fedora and Red

Hat. Be aware that the package may call docker-io on old OS releases. * Make sure that docker is up and running and the user that will run robottelo has permission to run docker commands. For more information check the docker installation guide * Pull the selenium/standalone-firefox image * Set browser=docker at the [robottelo] section in the configuration file

Once you’ve performed these steps, UI tests will no longer launch a web browser on your system. Instead, UI tests launch a web browser within a docker container.

Running UI Tests On SauceLabs

It is possible to run UI tests on SauceLabs. To do this:

  • Set browser=saucelabs at the [robottelo] section in the configuration

file * Select the browser type by setting webdriver at the [robottelo] section in the configuration file. Valid values are firefox, chrome and ie. * Fill saucelabs_user and saucelabs_key at the [robottelo] section in the configuration file with your Sauce OnDemand credentials. * If the machine where Satellite 6 is installed is on a VPN or behind a firewall make sure to have SauceConnect running.



committing code_standards reviewing_PRs features/index autoapi/index

Want to contribute? Before submitting code, read through the committing guide and Robottelo code standards. Ready to start reviewing pull requests? We have a guide for that too! Finally, the API reference covers individual functions, classes, methods and modules.

Robottelo is compatible with Python 3.6+.

Bugs are listed on GitHub. If you think you’ve found a new issue, please do one of the following:

  • Open a new bug report on Github.

  • Join the #robottelo IRC channel on Freenode (

You can generate the documentation for Robottelo as follows, so long as you have Sphinx and make installed:

$ cd docs
$ make html

You can generate a graph of Foreman entities and their dependencies, so long as you have graphviz installed:

$ make graph-entities

To check for code smells:

$ pre-commit install-hooks
$ pre-commit run --all-files

The design and development for this software is led by Og Maciel.