Development testing

Running the tests locally

In typesafety, every test (functional, integration, BDD, code style checks, etc.) is run using tox. The official list of supported Python versions are:

• 3.2
• 3.3
• 3.4

If you want to develop typesafety it is advisable that you have these versions installed on your machine (I suggest you download and compile the latest versions of these interpreters and install them somewhere). Unless you do this you won't be able to run the tests for those versions, but in most cases that is okay, since travis will catch any errors and let you fix them before sending a pull request, but if you do a lot of developing, this will be a lot faster.

Used tools

The following tools are used:

• nose
• mock (while mock is part of the module unittest as of Python 3.3, we need this to work on Python 3.2, so we still use the external variant).
• pep8 and pylint
• coverage
• behave

Requirements for pull requests

The requirements for a pull request to be merged are:

• Travis should pass on all platforms. The most important are Python 3.2 (Ubuntu 12.04LTS uses it) and Python 3.4 (most current distros use this version).
• The pull request should not break any pre-existing functionality (i.e. the tests and the behave features are not modified but extended). Note that typesafety is already used in testing production code and those should not break.