Developing and Testing

Our tests are inside tests/. Tests are implemented using pytest.

make test 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 git@github.com:tony/stripe_django.git
$ cd stripe_django

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

$ virtualenv .venv

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

$ source .venv/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.

$ stripe_django

Test Runner

As you seen above, the stripe_django 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 .venv folder with its own packages.

$ make test

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

$ py.test tests/test_common.py

will test the tests/test_common.py tests.

$ py.test tests/test_common.py::test_ignores_letter_versions

tests test_ignore_letter_versions() tests/test_common.py.

Multiple can be separated by spaces:

$ py.test tests/test_{window,pane}.py \
  tests/test_common.py::test_ignores_letter_versions

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 stripe_django project and into the virtualenv if you are using one, see details on installing the dev version of stripe_django above. Then:

    $ py.test tests/test_workspacebuilder.py
    

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

Run tests on save

You can re-run tests automatically on file edit.

Note

This requires entr(1).

Install entr. Packages are available available on most Linux and BSD variants, including Debian, Ubuntu, FreeBSD, OS X.

To run all tests upon editing any .py file:

$ make watch_test

Rebuild the documentation when an .rst file is edited:

$ cd doc
$ make watch

developer workflow

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

$ stripe_django load .

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

session_name: stripe-django
start_directory: ./ # load session relative to config location (project root).
before_script: ./bootstrap_env.py # ./ to load relative to project root.
windows:
- window_name: stripe-django
  focus: True
  layout: main-horizontal
  options:
    main-pane-height: 35
  shell_command_before:
    - '[ -d .venv -a -f .venv/bin/activate ] && source .venv/bin/activate'
  panes:
  - focus: true
  - pane 
  - make watch_flake8
  - make watch_test
- window_name: docs
  layout: main-horizontal
  options:
    main-pane-height: 35
  start_directory: docs/
  shell_command_before:
    - '[ -d ../.venv -a -f ../.venv/bin/activate ] && source ../.venv/bin/activate'
  panes:
  - focus: true
  - pane
  - make serve
  - make watch

Travis CI

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

stripe_django 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

sudo: false
python:
  - 2.7
  - 3.4
  - 3.5
before_install:
  - export PIP_USE_MIRRORS=true
  - pip install --upgrade pytest  # https://github.com/travis-ci/travis-ci/issues/4873
  - pip install --upgrade pip wheel virtualenv setuptools
  - pip install coveralls
install:
  - pip install -e .
script: coverage run --source=stripe_django setup.py test
after_success:
  - bash <(curl -s https://codecov.io/bash)