Revert '$' changes to not trigger regendoc
This commit is contained in:
parent
799bcccd1b
commit
5cf58a9ae9
|
@ -8,7 +8,7 @@ can change the pattern by issuing:
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
$ pytest --doctest-glob='*.rst'
|
||||
pytest --doctest-glob='*.rst'
|
||||
|
||||
on the command line. Since version ``2.9``, ``--doctest-glob``
|
||||
can be given multiple times in the command-line.
|
||||
|
@ -32,7 +32,7 @@ python test modules):
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
$ pytest --doctest-modules
|
||||
pytest --doctest-modules
|
||||
|
||||
You can make these changes permanent in your project by
|
||||
putting them into a pytest.ini file like this:
|
||||
|
@ -133,7 +133,7 @@ you want to continue the test even when you have failures, do:
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
$ pytest --doctest-modules --doctest-continue-on-failure
|
||||
pytest --doctest-modules --doctest-continue-on-failure
|
||||
|
||||
|
||||
.. _`doctest_namespace`:
|
||||
|
@ -183,8 +183,8 @@ by using one of standard doctest modules format in options
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
$ pytest --doctest-modules --doctest-report none
|
||||
$ pytest --doctest-modules --doctest-report udiff
|
||||
$ pytest --doctest-modules --doctest-report cdiff
|
||||
$ pytest --doctest-modules --doctest-report ndiff
|
||||
$ pytest --doctest-modules --doctest-report only_first_failure
|
||||
pytest --doctest-modules --doctest-report none
|
||||
pytest --doctest-modules --doctest-report udiff
|
||||
pytest --doctest-modules --doctest-report cdiff
|
||||
pytest --doctest-modules --doctest-report ndiff
|
||||
pytest --doctest-modules --doctest-report only_first_failure
|
||||
|
|
|
@ -60,7 +60,7 @@ Example:
|
|||
|
||||
.. code-block:: pytest
|
||||
|
||||
$ pytest path_a path_a
|
||||
pytest path_a path_a
|
||||
|
||||
...
|
||||
collected 1 item
|
||||
|
@ -73,7 +73,7 @@ Example:
|
|||
|
||||
.. code-block:: pytest
|
||||
|
||||
$ pytest --keep-duplicates path_a path_a
|
||||
pytest --keep-duplicates path_a path_a
|
||||
|
||||
...
|
||||
collected 2 items
|
||||
|
@ -85,7 +85,7 @@ Example:
|
|||
|
||||
.. code-block:: pytest
|
||||
|
||||
$ pytest test_a.py test_a.py
|
||||
pytest test_a.py test_a.py
|
||||
|
||||
...
|
||||
collected 2 items
|
||||
|
@ -180,7 +180,7 @@ example if you have unittest2 installed you can type:
|
|||
|
||||
.. code-block:: bash
|
||||
|
||||
$ pytest --pyargs unittest2.test.test_skipping -q
|
||||
pytest --pyargs unittest2.test.test_skipping -q
|
||||
|
||||
which would run the respective test module. Like with
|
||||
other options, through an ini-file and the :confval:`addopts` option you
|
||||
|
@ -203,7 +203,7 @@ You can always peek at the collection tree without running tests like this:
|
|||
|
||||
.. code-block:: pytest
|
||||
|
||||
$ pytest --collect-only pythoncollection.py
|
||||
. $ pytest --collect-only pythoncollection.py
|
||||
=========================== test session starts ============================
|
||||
platform linux -- Python 3.x.y, pytest-4.x.y, py-1.x.y, pluggy-0.x.y
|
||||
cachedir: $PYTHON_PREFIX/.pytest_cache
|
||||
|
@ -263,7 +263,7 @@ leave out the ``setup.py`` file:
|
|||
|
||||
.. code-block:: pytest
|
||||
|
||||
$ pytest --collect-only
|
||||
#$ pytest --collect-only
|
||||
====== test session starts ======
|
||||
platform linux2 -- Python 2.7.10, pytest-2.9.1, py-1.4.31, pluggy-0.3.1
|
||||
rootdir: $REGENDOC_TMPDIR, inifile: pytest.ini
|
||||
|
|
Loading…
Reference in New Issue