[svn r37992] have real definitions (yes, the empty lines make a difference). rest is strange.
--HG-- branch : trunk
This commit is contained in:
parent
d45b45a74e
commit
157a77ef0a
|
@ -377,23 +377,19 @@ Regular options
|
|||
---------------
|
||||
|
||||
``-v, --verbose``
|
||||
|
||||
Increase verbosity. This shows a test per line while running and also
|
||||
shows the traceback after interrupting the test run with Ctrl-C.
|
||||
|
||||
|
||||
``-x, --exitfirst``
|
||||
|
||||
exit instantly on the first error or the first failed test.
|
||||
|
||||
|
||||
``-s, --nocapture``
|
||||
|
||||
disable catching of sys.stdout/stderr output.
|
||||
|
||||
|
||||
``-k KEYWORD``
|
||||
|
||||
only run test items matching the given keyword expression. You can also add
|
||||
use ``-k -KEYWORD`` to exlude tests from being run. The keyword is matched
|
||||
against filename, test class name, method name.
|
||||
|
@ -405,37 +401,31 @@ Regular options
|
|||
|
||||
|
||||
``--pdb``
|
||||
|
||||
drop into pdb (the `Python debugger`_) on exceptions. If the debugger is
|
||||
quitted, the next test is run. This implies ``-s``.
|
||||
|
||||
|
||||
``--tb=TBSTYLE``
|
||||
|
||||
traceback verboseness: ``long`` is the default, ``short`` are the normal
|
||||
Python tracebacks, ``no`` omits tracebacks completely.
|
||||
|
||||
|
||||
``--fulltrace``
|
||||
|
||||
Don't cut any tracebacks. The default is to leave out frames if an infinite
|
||||
recursion is detected.
|
||||
|
||||
|
||||
``--nomagic``
|
||||
|
||||
Refrain from using magic as much as possible. This can be useful if you are
|
||||
suspicious that ``py.test`` somehow interferes with your program in
|
||||
unintended ways (if this is the case, please contact us!).
|
||||
|
||||
|
||||
``--collectonly``
|
||||
|
||||
Only collect tests, don't execute them.
|
||||
|
||||
|
||||
``--traceconfig``
|
||||
|
||||
trace considerations of conftest.py files. Useful when you have various
|
||||
conftest.py files around and are unsure about their interaction.
|
||||
|
||||
|
@ -447,7 +437,6 @@ experimental options
|
|||
|
||||
|
||||
``-f, --looponfailing``
|
||||
|
||||
Loop on failing test set. This is a feature you can use when you are trying
|
||||
to fix a number of failing tests: First all the tests are being run. If a
|
||||
number of tests are failing, these are run repeatedly afterwards. Every
|
||||
|
@ -456,34 +445,28 @@ experimental options
|
|||
it is removed from the test set.
|
||||
|
||||
``--exec=EXECUTABLE``
|
||||
|
||||
Python executable to run the tests with. Useful for testing on different
|
||||
versions of Python.
|
||||
|
||||
|
||||
``-d, --dist``
|
||||
|
||||
ad-hoc `distribute tests across machines`_ (requires conftest settings)
|
||||
|
||||
|
||||
``-w, --startserver``
|
||||
|
||||
starts local web server for displaying test progress.
|
||||
|
||||
|
||||
``-r, --runbrowser``
|
||||
|
||||
Run browser (implies --startserver).
|
||||
|
||||
|
||||
``--box``
|
||||
|
||||
Use boxing: run each test in an external process. Very useful for testing
|
||||
things that occasionally segfault (since normally the segfault then would
|
||||
stop the whole test process).
|
||||
|
||||
``--rest``
|
||||
|
||||
`reStructured Text`_ output reporting.
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue