summaryrefslogtreecommitdiff
path: root/docs/development.rst
diff options
context:
space:
mode:
authorJannis Leidel <jannis@leidel.info>2019-10-18 15:57:13 +0200
committerGitHub <noreply@github.com>2019-10-18 15:57:13 +0200
commitf6bf14afd22d8e5b706670590cc95f29d4483434 (patch)
treea65fbc8b6fd1112222beb6f66c31082ffe231460 /docs/development.rst
parentf3d02aa3b088e2f9044fe5e4869e8c8cb91d2cdc (diff)
downloadtablib-f6bf14afd22d8e5b706670590cc95f29d4483434.tar.gz
Add project release config and cleanup project setup. (#398)
* Add project release config and use Travis build stages. Refs #378. * Restructure project to use src/ and tests/ directories. * Fix testing. * Remove eggs. * More fixes. - isort and flake8 config - manifest template update - tox ini extension - docs build fixes - docs content fixes * Docs and license cleanup.
Diffstat (limited to 'docs/development.rst')
-rw-r--r--docs/development.rst26
1 files changed, 1 insertions, 25 deletions
diff --git a/docs/development.rst b/docs/development.rst
index 83fd159..c481d0d 100644
--- a/docs/development.rst
+++ b/docs/development.rst
@@ -150,31 +150,7 @@ the easiest way to test your changes for potential issues is to simply run the t
.. code-block:: console
- $ ./test_tablib.py
-
-
-`Jenkins CI`_, amongst other tools, supports Java's xUnit testing report format.
-Nose_ allows us to generate our own xUnit reports.
-
-Installing nose is simple.
-
-.. code-block:: console
-
- $ pip install nose
-
-Once installed, we can generate our xUnit report with a single command.
-
-.. code-block:: console
-
- $ nosetests test_tablib.py --with-xunit
-
-This will generate a **nosetests.xml** file, which can then be analyzed.
-
-.. _Nose: https://github.com/nose-devs/nose
-
-
-
-.. _jenkins:
+ $ tox
----------------------
Continuous Integration