jiuyuan
/
test_ok1
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix practise -> practice typo in documentation

This commit is contained in:
Loïc Estève 2016-01-20 16:35:27 +01:00
parent 11a7bcaaa5
commit 99072ea8c9
6 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@ -60,7 +60,7 @@ Features
- Detailed info on failing `assert statements <http://pytest.org/latest/assert.html>`_ (no need to remember ``self.assert*`` names); - Detailed info on failing `assert statements <http://pytest.org/latest/assert.html>`_ (no need to remember ``self.assert*`` names);
- `Auto-discovery - `Auto-discovery
<http://pytest.org/latest/goodpractises.html#python-test-discovery>`_ <http://pytest.org/latest/goodpractices.html#python-test-discovery>`_
of test modules and functions; of test modules and functions;
- `Modular fixtures <http://pytest.org/latest/fixture.html>`_ for - `Modular fixtures <http://pytest.org/latest/fixture.html>`_ for

2
doc/en/getting-started.rst
View File

@ -193,7 +193,7 @@ Where to go next
Here are a few suggestions where to go next: Here are a few suggestions where to go next:
* :ref:`cmdline` for command line invocation examples * :ref:`cmdline` for command line invocation examples
* :ref:`good practises <goodpractises>` for virtualenv, test layout, genscript support * :ref:`good practices <goodpractices>` for virtualenv, test layout, genscript support
* :ref:`fixtures` for providing a functional baseline to your tests * :ref:`fixtures` for providing a functional baseline to your tests
* :ref:`apiref` for documentation and examples on using ``pytest`` * :ref:`apiref` for documentation and examples on using ``pytest``
* :ref:`plugins` managing and writing plugins * :ref:`plugins` managing and writing plugins

2
doc/en/goodpractises.rst → doc/en/goodpractices.rst
View File

@ -1,5 +1,5 @@
.. highlightlang:: python .. highlightlang:: python
.. _`goodpractises`: .. _`goodpractices`:
Good Integration Practices Good Integration Practices
================================================= =================================================

2
doc/en/index.rst
View File

@ -40,7 +40,7 @@ pytest: helps you write better programs
- multi-paradigm: pytest can run ``nose``, ``unittest`` and - multi-paradigm: pytest can run ``nose``, ``unittest`` and
``doctest`` style test suites, including running testcases made for ``doctest`` style test suites, including running testcases made for
Django and trial Django and trial
- supports :ref:`good integration practises <goodpractises>` - supports :ref:`good integration practices <goodpractices>`
- supports extended :ref:`xUnit style setup <xunitsetup>` - supports extended :ref:`xUnit style setup <xunitsetup>`
- supports domain-specific :ref:`non-python tests` - supports domain-specific :ref:`non-python tests`
- supports generating `test coverage reports - supports generating `test coverage reports

2
doc/en/overview.rst
View File

@ -7,7 +7,7 @@ Getting started basics
getting-started getting-started
usage usage
goodpractises goodpractices
projects projects
faq faq

2
doc/en/writing_plugins.rst
View File

@ -95,7 +95,7 @@ Here is how you might run it::
python package directory (i.e. one containing an ``__init__.py``) then python package directory (i.e. one containing an ``__init__.py``) then
"import conftest" can be ambiguous because there might be other "import conftest" can be ambiguous because there might be other
``conftest.py`` files as well on your PYTHONPATH or ``sys.path``. ``conftest.py`` files as well on your PYTHONPATH or ``sys.path``.
It is thus good practise for projects to either put ``conftest.py`` It is thus good practice for projects to either put ``conftest.py``
under a package scope or to never import anything from a under a package scope or to never import anything from a
conftest.py file. conftest.py file.