[svn r38118] there is no gurantee anymore that tests run in order
--HG-- branch : trunk
This commit is contained in:
parent
1a33d1eae6
commit
1390114d82
|
@ -183,18 +183,13 @@ The catching of stdout/stderr output can be disabled using the
|
||||||
``--nocapture`` option to the ``py.test`` tool. Any output will
|
``--nocapture`` option to the ``py.test`` tool. Any output will
|
||||||
in this case be displayed as soon as it is generated.
|
in this case be displayed as soon as it is generated.
|
||||||
|
|
||||||
order of execution is guaranteed
|
test execution order
|
||||||
--------------------------------
|
--------------------------------
|
||||||
|
|
||||||
Tests will run in the order in which they appear in the files.
|
Tests usually run in the order in which they appear in the files.
|
||||||
If you invoke ``py.test`` multiple times you should find that tests
|
However, tests should not rely on running one after another, as
|
||||||
execute in exactly the same order within each file.
|
this prevents more advanced usages: running tests
|
||||||
|
distributedly or selectively, or in "looponfailing" mode.
|
||||||
Besides making it easier to compare test output this allows
|
|
||||||
multi-stage tests where you can rely on your test to iteratively
|
|
||||||
build up a test structure.
|
|
||||||
|
|
||||||
`Note: This is not true for distributed tests`
|
|
||||||
|
|
||||||
useful tracebacks, recursion detection
|
useful tracebacks, recursion detection
|
||||||
--------------------------------------
|
--------------------------------------
|
||||||
|
|
Loading…
Reference in New Issue