summaryrefslogtreecommitdiff
path: root/doc/example/pytest.txt
diff options
context:
space:
mode:
authorholger krekel <holger@merlinux.eu>2010-07-02 10:05:00 +0200
committerholger krekel <holger@merlinux.eu>2010-07-02 10:05:00 +0200
commit2ec58e23038f9e33f5b376992b60586f0806fd7a (patch)
tree9bb457530571a87e573b762ba1776072224704e3 /doc/example/pytest.txt
parente00a0e970c6bc48bbbd5b6482f9914b7b3b71259 (diff)
downloadtox-2ec58e23038f9e33f5b376992b60586f0806fd7a.tar.gz
overhaul and extension and improved docs for substitutions in ini files
Diffstat (limited to 'doc/example/pytest.txt')
-rw-r--r--doc/example/pytest.txt14
1 files changed, 10 insertions, 4 deletions
diff --git a/doc/example/pytest.txt b/doc/example/pytest.txt
index 823bbd1..fe0a630 100644
--- a/doc/example/pytest.txt
+++ b/doc/example/pytest.txt
@@ -5,7 +5,8 @@ py.test and tox
.. _`py.test`: http://pytest.org
It is easy to integrate `py.test`_ runs with tox. If you encounter
-any issues use the :doc:`support` channels.
+issues, please check if they are `listed as a known issue`_ and/or use
+the :doc:`support channels <../support>`.
Basic py.test example for "extra" test directories
--------------------------------------------------------------
@@ -45,11 +46,13 @@ to make ``tox`` use this feature::
--confcutdir=.. # stop looking for conftest files at parent dir
-n 3 # use three sub processes
+.. _`pytest-xdist`: http://codespeak.net/py/dist/test/plugin/xdist.html
+
Using tox, py.test and the Hudson CI
-------------------------------------------
The Hudson_ continous integration server allows to define "jobs" with
-"build steps" which can be test invocations. If you :doc:`install` ``tox`` on your
+"build steps" which can be test invocations. If you :doc:`install <../install>` ``tox`` on your
default Python installation on each slave, you can then have a
Hudson test build step invoke tox from a Python script like this::
@@ -68,12 +71,15 @@ for your ``argv`` parameter::
and then configure your Hudson job to collect "JUnit test results" with the ``**/junit-*.xml`` pattern.
For a real-life example see `py.test own Hudson job configuration`_. This actually
-uses a "Parametrized Hudson built" which provides a nice configuration matrix
+uses a "Parametrized Hudson build" which provides a nice configuration matrix
and lets ``tox`` handle all the underlying work of preparing and running things.
.. _`py.test own Hudson job configuration`: http://hudson.testrun.org/view/pytest/job/pytest-multi/configure
+.. _`Hudson`: http://hudson-ci.org/
+
+.. _`listed as a known issue`:
-Issues and limitations
+Known Issues and limitations
-----------------------------
* tox does not work on the Windows/Python3/Virtualenv3 combination due to limitations of the virtualenv3 project