2017-09-22 18:16:35 +00:00
|
|
|
# Warning
|
|
|
|
|
|
|
|
This directory is full of disorganized crap, including random hacks I checked
|
|
|
|
in that I'd like to turn into tests. The effort to write tests only really
|
|
|
|
started in September 2017. Pull requests in this area are very welcome!
|
2018-03-06 11:22:14 +00:00
|
|
|
|
|
|
|
|
|
|
|
## Running The Tests
|
|
|
|
|
|
|
|
[![Build Status](https://api.travis-ci.org/dw/mitogen.svg?branch=master)](https://travis-ci.org/dw/mitogen)
|
|
|
|
|
|
|
|
Your computer should have an Internet connection, and the ``docker`` command
|
|
|
|
line tool should be able to connect to a working Docker daemon (localhost or
|
|
|
|
elsewhere for OS X etc.) that can run new images.
|
|
|
|
|
|
|
|
The IP address of the Docker daemon must allow exposing ports from running
|
|
|
|
containers, e.g. it should not be firewalled or port forwarded.
|
|
|
|
|
|
|
|
If in doubt, just install Docker on a Linux box in the default configuration
|
|
|
|
and run the tests there.
|
|
|
|
|
|
|
|
## Steps To Prepare Development Environment
|
|
|
|
|
|
|
|
1. Get the code ``git clone https://github.com/dw/mitogen.git``
|
|
|
|
1. Go into the working directory ``cd mitogen``
|
|
|
|
1. Establish the docker image ``./tests/build_docker_image.py``
|
|
|
|
1. Build the virtual environment ``virtualenv ../venv``
|
|
|
|
1. Enable the virtual environment we just built ``source ../venv/bin/activate``
|
|
|
|
1. Install Mitogen in pip editable mode ``pip install -e .``
|
2018-04-01 00:42:31 +00:00
|
|
|
1. Run ``test``
|