Salt configuration for building a headless server capable of running Selenium tests
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


This project provides a Salt configuration and supporting scripts to build out a group of headless testing servers leveraging the Selenium browser automation tool.

The repository as released provides the exact functionality used by its lead developer for testing a WebRTC application powered by FreeSWITCH and Janus. You can see some examples of the tool in action here and here.

It is meant to be forked as a starting point for others with similar needs.

Key features

  • Full end user environment through Google Chrome automation.
  • Example Selenium tests written in Python.
  • VNC access to the server's Xfce windowing environment.
  • Simulate different end user network conditions via the PyLTC traffic shaping tool.
  • Automated setup of many standard server components (firewall, network, users, etc.).
  • Local developemnt of the testing server itself via Vagrant.


Some familiarity with the Salt server configuration tool and shell scripting is required to get the most out of this project.

See for details.

Managing tests

By default, the tests and supporting code at salt/salt/custom/tests is installed to /home/test/tests on all testing servers. The test running scripts discussed below depend on finding tests in this location, with the naming pattern [name] To add/remove tests of your own, write Salt states that place your test files in /home/test/tests -- see salt/salt/custom/tests/init.sls as an example of how to do this.

Currently only Python tests are available as examples, but tests in other languages should work fine as well, provided the correct Selenium driver for the language is installed.

Some generally useful testing helpers can be found in salt/salt/custom/tests/, including those related to traffic shaping via PyLTC

Running tests

From a testing server

The installed,, and scripts can be used to run, kill, and pause tests directly from a testing server. They are executed with one argument, the name of the test to run, leaving off the suffix. For example, to run, execute foo.

From the master

The production/ script symlinks all scripts in production/scripts to /usr/local/bin. They provide a simple method to manage up to ten testing servers at once, by executing the individual test management script on multiple test servers. Edit the SERVER_NAME_TEMPLATE variable at the top of each script to match the naming pattern of the minion IDs on your testing servers, and run the script without arguments for usage instructions.


  • Everything under the salt/salt/custom directory are resources specifically used by the lead developer in their testing environment. They are included in the repository for convenience, and can be used or removed as needed without compromising the overall functionality of the server.


The issue tracker for this project is provided to file bug reports, feature requests, and project tasks -- support requests are not accepted via the issue tracker. For all support-related issues, including configuration, usage, and training, consider hiring a competent consultant.