summaryrefslogtreecommitdiff
path: root/functional_tests
diff options
context:
space:
mode:
authorJason Pellerin <jpellerin@gmail.com>2009-01-14 16:54:50 +0000
committerJason Pellerin <jpellerin@gmail.com>2009-01-14 16:54:50 +0000
commitefb4cc9d8db8a7f912934f2c5b89ed1ddffc1342 (patch)
tree8b4925ffdfa9e6d08c1ed85100093454c4a2064f /functional_tests
parent639d3bd64c8218b4377114eabf72d9f703c323aa (diff)
downloadnose-efb4cc9d8db8a7f912934f2c5b89ed1ddffc1342.tar.gz
Added some warnings about plugin interoperation
Diffstat (limited to 'functional_tests')
-rw-r--r--functional_tests/doc_tests/test_multiprocess/multiprocess.rst9
1 files changed, 9 insertions, 0 deletions
diff --git a/functional_tests/doc_tests/test_multiprocess/multiprocess.rst b/functional_tests/doc_tests/test_multiprocess/multiprocess.rst
index e6914eb..3a75a40 100644
--- a/functional_tests/doc_tests/test_multiprocess/multiprocess.rst
+++ b/functional_tests/doc_tests/test_multiprocess/multiprocess.rst
@@ -222,6 +222,14 @@ differences that may also impact your test suite:
output. Since difference processes may complete their tests at different
times, test result output order is not determinate.
+* Plugin interaction warning
+
+ The multiprocess plugin does not work well with other plugins that expect to
+ wrap or gain control of the test-running process. Examples from nose's
+ builtin plugins include coverage and profiling: a test run using
+ both multiprocess and either of those is likely to fail in some
+ confusing and spectacular way.
+
* Python 2.6 warning
This is unlikely to impact you unless you are writing tests for nose itself,
@@ -230,3 +238,4 @@ differences that may also impact your test suite:
use subprocess to launch another copy of nose that also uses the
multiprocess plugin. This is why this test is skipped under python 2.6 when
run with the --processes switch.
+