Running Fabric’s Tests¶
Fabric is maintained with 100% passing tests. Where possible, patches should include tests covering the changes, making things far easier to verify & merge.
When developing on Fabric, it works best to establish a virtualenv to install the dependencies in isolation for running tests.
- Fork the repository on GitHub
- Clone your new fork (e.g.
git clone firstname.lastname@example.org:<your_username>/fabric.git)
pip install -r requirements.txt
python setup.py develop
Once your virtualenv is activated (
. env/bin/activate) & you have the latest
requirements, running tests is just:
You should always run tests on
master (or the release branch you’re
working with) to ensure they’re passing before working on your own
Alternatively, if you’ve run
python setup.py develop on your Fabric clone,
you can also run:
This adds additional flags which enable running doctests & adds nice coloration.