Browse files

DOC: document how to run slow tests

  • Loading branch information...
pv committed Jan 25, 2014
1 parent 357375c commit 8778612accde48d1260bead4d5d8e7f8c3fbf98b
Showing with 19 additions and 0 deletions.
  1. +19 −0 HACKING.rst.txt
@@ -197,6 +197,9 @@ Using ```` is the recommended approach to running tests.
There are also a number of alternatives to it, for example in-place
build or installing to a virtualenv. See the FAQ below for details.
+Some of the tests in Scipy are very slow and need to be separately
+enabled. See the FAQ below for details.
SciPy structure
@@ -391,6 +394,22 @@ course use your favourite alternative debugger; run it on the
``python`` binary with arguments `` -g --python``.
+*How do I enable additional tests in Scipy?*
+Some of the tests in Scipy's test suite are very slow and not enabled
+by default. You can run the full suite via::
+ $ python -g -m full
+This invokes the test suite ``import scipy; scipy.test("full")``,
+enabling also slow tests.
+There is an additional level of very slow tests (several minutes),
+which are disabled also in this case. They can be enabled by setting
+the environment variable ``SCIPY_XSLOW=1`` before running the test
.. _scikit-learn:
.. _scikits-image:

0 comments on commit 8778612

Please sign in to comment.