tmuxp is usable but still needs your help reporting errors, bugs and usability feedback. If you encounter an error, please post on the Issue tracker.

Developing and Testing

Our tests are inside ./tmuxp/testsuite. Tests are implemented using unittest.

./ will create a tmux server on a separate socket_name using $ tmux -L test_case.

Install the latest code from git

To begin developing, check out the code from github:

$ git clone
$ cd tmuxp

Now create a virtualenv, if you don’t know how to, you can create a virtualenv with:

$ virtualenv .env

Then activate it to your current tty / terminal session with:

$ source .env/bin/activate

Good! Now let’s run this:

$ pip install -e .

This has pip, a python package manager install the python package in the current directory. -e means --editable, which means you can adjust the code and the installed software will reflect the changes.

$ tmuxp

Test Runner

As you seen above, the tmuxp command will now be available to you, since you are in the virtual environment, your PATH environment was updated to include a special version of python inside your .env folder with its own packages.

$ ./

You probably didn’t see anything but tests scroll by.

If you found a problem or are trying to write a test, you can file an issue on github.

Test runner options


As of v0.1.1, the old way of using --tests is now deprecated.

Testing specific TestSuites and TestCase.

$ ./ config

will test the testsuite.config unittest.TestSuite.

$ ./ config.ImportExportTest

tests testsuite.config.ImportExportTest unittest.TestCase.

individual tests:

$ ./ config.ImportExportTest.test_export_json

Multiple can be separated by spaces:

$ ./ window pane config.ImportExportTest

Visual testing

You can watch tmux testsuite build sessions visually by keeping a client open in a separate terminal.

Create two terminals:

  • Terminal 1: $ tmux -L test_case

  • Terminal 2: $ cd into the tmuxp project and into the virtualenv if you are using one, see details on installing the dev version of tmuxp above. Then:

    $ python ./ --tests tests_workspacebuilder

Terminal 1 should have flickered and built the session before your eyes. tmuxp hides this building from normal users.

Run tests on save

You can re-run tests automatically on file edit.


This requires and installation of sniffer from pypi.

Install sniffer from pypi:

$ pip install sniffer

To run all tests upon editing any .py file:

$ sniffer

tmuxp developer config


After you Install the latest code from git, when inside the tmuxp checkout:

$ tmuxp load .

this will load the .tmuxp.yaml in the root of the project.

session_name: tmuxp
start_directory: ./ # load session relative to config location (project root).
before_script: ./ # ./ to load relative to project root.
- window_name: tmuxp
  focus: True
  layout: main-horizontal
    main-pane-height: 35
    - '[ -d .env -a -f .env/bin/activate ] && source .env/bin/activate'
  - focus: true
  - pane 
  - sniffer
- window_name: docs
  layout: main-horizontal
    main-pane-height: 35
  start_directory: doc/
    - '[ -d ../.env -a -f ../.env/bin/activate ] && source ../.env/bin/activate'
  - focus: true
  - pane
  - echo 'docs built to <>'; python -m SimpleHTTPServer 8003
  - sniffer

Travis CI

tmuxp uses travis-ci for continuous integration / automatic unit testing.

tmuxp is tested against tmux 1.8 and the latest git source. Interpretters tested are 2.6, 2.7 and 3.3. The travis build site uses this .travis.yml configuration:

language: python

  - 2.6
  - 2.7
  - 3.3
  - TMUX_VERSION=master
  - sudo apt-get update -qq
  - export PIP_USE_MIRRORS=true
  - pip install coveralls
  - "pip install -e ."
  - sudo apt-get install -qq libevent-dev libncurses-dev
  - git clone git:// tmux
  - cd tmux
  - git checkout $TMUX_VERSION
  - sh
  - ./configure && make && sudo make install
  - cd ..
  - tmux -V
script: coverage run --source=tmuxp test
# script: python test
  - coveralls