-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Unify running unit tests under unittest2
There are three ways to run the tests. This is unfortunate, but with this commit they're all going through the same code paths. * As a developer, use "python setup.py test". This runs them in the current development directory and does not require a virtualenv to be set up. * As a contributor, your pull requests will be tested on Travis CI. The configuration for that is in .travis.yml. This runs the test suite on all supported platforms. * As a release maintainer, install tox (in a virtualenv?) and run "tox" in the toplevel Park source tree to build a source distribution and run the test suite on supported platforms.
- Loading branch information
Showing
5 changed files
with
36 additions
and
38 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,4 @@ | ||
include README.rst LICENSE test_park.py | ||
include README.rst | ||
include LICENSE | ||
include test_park.py | ||
include test-requirements.txt |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
Welcome! | ||
|
||
There are three ways the Park unit test suite is run. | ||
|
||
As a *developer*, use ``python setup.py test``. This runs the suite in | ||
the current development directory and does not require a virtualenv to | ||
be set up. | ||
|
||
As a *contributor*, your Github pull requests will be tested on Travis | ||
CI. The configuration for that is in .travis.yml. This runs the test | ||
suite on all supported platforms, which are enumerated in that file. | ||
|
||
As a *release maintainer*, install ``tox`` (in a virtualenv is fine) | ||
and run it in the top level Park source directory. This will build a | ||
source distribution, install that into a virtualenv for each supported | ||
platform, and run the test suite in each. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters