Reworded titles of some clear how-to guides
Files retitled: assert.rst bash-completion.rst capture.rst existingtestsuite.rst mark.rst monkeypatch.rst nose.rst parametrize.rst plugins.rst skipping.rst tmpdir.rst usage.rst
This commit is contained in:
parent
4a19533ba5
commit
d2d975d6cf
|
@ -1,5 +1,5 @@
|
||||||
|
|
||||||
The writing and reporting of assertions in tests
|
How to write and report assertions in tests
|
||||||
==================================================
|
==================================================
|
||||||
|
|
||||||
.. _`assertfeedback`:
|
.. _`assertfeedback`:
|
||||||
|
|
|
@ -1,8 +1,8 @@
|
||||||
|
|
||||||
.. _bash_completion:
|
.. _bash_completion:
|
||||||
|
|
||||||
Setting up bash completion
|
How to set up bash completion
|
||||||
==========================
|
=============================
|
||||||
|
|
||||||
When using bash as your shell, ``pytest`` can use argcomplete
|
When using bash as your shell, ``pytest`` can use argcomplete
|
||||||
(https://argcomplete.readthedocs.io/) for auto-completion.
|
(https://argcomplete.readthedocs.io/) for auto-completion.
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
|
|
||||||
.. _`captures`:
|
.. _`captures`:
|
||||||
|
|
||||||
Capturing of the stdout/stderr output
|
How to capture stdout/stderr output
|
||||||
=========================================================
|
=========================================================
|
||||||
|
|
||||||
Default stdout/stderr/stdin capturing behaviour
|
Default stdout/stderr/stdin capturing behaviour
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
.. _existingtestsuite:
|
.. _existingtestsuite:
|
||||||
|
|
||||||
Using pytest with an existing test suite
|
How to use pytest with an existing test suite
|
||||||
===========================================
|
==============================================
|
||||||
|
|
||||||
Pytest can be used with most existing test suites, but its
|
Pytest can be used with most existing test suites, but its
|
||||||
behavior differs from other test runners such as :ref:`nose <noseintegration>` or
|
behavior differs from other test runners such as :ref:`nose <noseintegration>` or
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
.. _mark:
|
.. _mark:
|
||||||
|
|
||||||
Marking test functions with attributes
|
How to mark test functions with attributes
|
||||||
======================================
|
===========================================
|
||||||
|
|
||||||
By using the ``pytest.mark`` helper you can easily set
|
By using the ``pytest.mark`` helper you can easily set
|
||||||
metadata on your test functions. You can find the full list of builtin markers
|
metadata on your test functions. You can find the full list of builtin markers
|
||||||
|
|
|
@ -1,5 +1,5 @@
|
||||||
|
|
||||||
Monkeypatching/mocking modules and environments
|
How to monkeypatch/mock modules and environments
|
||||||
================================================================
|
================================================================
|
||||||
|
|
||||||
.. currentmodule:: _pytest.monkeypatch
|
.. currentmodule:: _pytest.monkeypatch
|
||||||
|
|
|
@ -1,6 +1,6 @@
|
||||||
.. _`noseintegration`:
|
.. _`noseintegration`:
|
||||||
|
|
||||||
Running tests written for nose
|
How to run tests written for nose
|
||||||
=======================================
|
=======================================
|
||||||
|
|
||||||
``pytest`` has basic support for running tests written for nose_.
|
``pytest`` has basic support for running tests written for nose_.
|
||||||
|
|
|
@ -6,7 +6,7 @@
|
||||||
|
|
||||||
.. _`parametrize-basics`:
|
.. _`parametrize-basics`:
|
||||||
|
|
||||||
Parametrizing fixtures and test functions
|
How to parametrize fixtures and test functions
|
||||||
==========================================================================
|
==========================================================================
|
||||||
|
|
||||||
pytest enables test parametrization at several levels:
|
pytest enables test parametrization at several levels:
|
||||||
|
|
|
@ -2,8 +2,8 @@
|
||||||
.. _`extplugins`:
|
.. _`extplugins`:
|
||||||
.. _`using plugins`:
|
.. _`using plugins`:
|
||||||
|
|
||||||
Installing and Using plugins
|
How to install and use plugins
|
||||||
============================
|
===============================
|
||||||
|
|
||||||
This section talks about installing and using third party plugins.
|
This section talks about installing and using third party plugins.
|
||||||
For writing your own plugins, please refer to :ref:`writing-plugins`.
|
For writing your own plugins, please refer to :ref:`writing-plugins`.
|
||||||
|
|
|
@ -2,8 +2,8 @@
|
||||||
|
|
||||||
.. _skipping:
|
.. _skipping:
|
||||||
|
|
||||||
Skip and xfail: dealing with tests that cannot succeed
|
How to use skip and xfail to deal with tests that cannot succeed
|
||||||
======================================================
|
=================================================================
|
||||||
|
|
||||||
You can mark test functions that cannot be run on certain platforms
|
You can mark test functions that cannot be run on certain platforms
|
||||||
or that you expect to fail so pytest can deal with them accordingly and
|
or that you expect to fail so pytest can deal with them accordingly and
|
||||||
|
|
|
@ -2,8 +2,8 @@
|
||||||
.. _`tmpdir handling`:
|
.. _`tmpdir handling`:
|
||||||
.. _tmpdir:
|
.. _tmpdir:
|
||||||
|
|
||||||
Temporary directories and files
|
How to use temporary directories and files in tests
|
||||||
================================================
|
===================================================
|
||||||
|
|
||||||
The ``tmp_path`` fixture
|
The ``tmp_path`` fixture
|
||||||
------------------------
|
------------------------
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
|
|
||||||
.. _usage:
|
.. _usage:
|
||||||
|
|
||||||
Usage and Invocations
|
How to invoke pytest
|
||||||
==========================================
|
==========================================
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue