Add suggestion to dev docs for debugging odd test failures
Adds information about the -r flag for tox to refresh the venv when running unitests as when this happens the failures can look odd or valid failures can be missing when running on a local system but occur when running in the gate. Change-Id: Ie6f7f73dfdbd4e55e8ac0b8a66cf9661f5630a09
This commit is contained in:
@@ -48,6 +48,16 @@ To run the `ValidateIntegerTestCase.test_invalid_inputs` test method in
|
|||||||
|
|
||||||
tox -epy27 test_utils.ValidateIntegerTestCase.test_invalid_inputs
|
tox -epy27 test_utils.ValidateIntegerTestCase.test_invalid_inputs
|
||||||
|
|
||||||
|
Debugging strange test failures
|
||||||
|
-------------------------------
|
||||||
|
|
||||||
|
Things to try when there are odd test failures such as failure on
|
||||||
|
jenkins but not locally.
|
||||||
|
|
||||||
|
The venv can get stale. Force a refresh by adding the -r flag::
|
||||||
|
|
||||||
|
tox -r -e pep8
|
||||||
|
|
||||||
.. rubric:: Footnotes
|
.. rubric:: Footnotes
|
||||||
|
|
||||||
.. [#f1] See :doc:`jenkins`.
|
.. [#f1] See :doc:`jenkins`.
|
||||||
|
|||||||
Reference in New Issue
Block a user