fix typos in docs
This commit is contained in:
marc
parent
8be9684ab2
commit
536177bb56
|
|
@ -117,7 +117,7 @@ It provide tools to raise money and share your finances in full transparency.
|
|||
It is the platform of choice for individuals and companies that want to make one-time or
|
||||
monthly donations directly to the project.
|
||||
|
||||
See more datails in the `pytest collective`_.
|
||||
See more details in the `pytest collective`_.
|
||||
|
||||
.. _Open Collective: https://opencollective.com
|
||||
.. _pytest collective: https://opencollective.com/pytest
|
||||
|
|
|
|||
|
|
@ -3,13 +3,13 @@ pytest-2.3: improved fixtures / better unittest integration
|
|||
|
||||
pytest-2.3 comes with many major improvements for fixture/funcarg management
|
||||
and parametrized testing in Python. It is now easier, more efficient and
|
||||
more predicatable to re-run the same tests with different fixture
|
||||
more predictable to re-run the same tests with different fixture
|
||||
instances. Also, you can directly declare the caching "scope" of
|
||||
fixtures so that dependent tests throughout your whole test suite can
|
||||
re-use database or other expensive fixture objects with ease. Lastly,
|
||||
it's possible for fixture functions (formerly known as funcarg
|
||||
factories) to use other fixtures, allowing for a completely modular and
|
||||
re-useable fixture design.
|
||||
re-usable fixture design.
|
||||
|
||||
For detailed info and tutorial-style examples, see:
|
||||
|
||||
|
|
|
|||
|
|
@ -91,7 +91,7 @@ holger krekel
|
|||
it might be the cause for other finalizers to fail.
|
||||
|
||||
- fix ordering when mock.patch or other standard decorator-wrappings
|
||||
are used with test methods. This fixues issue346 and should
|
||||
are used with test methods. This fixes issue346 and should
|
||||
help with random "xdist" collection failures. Thanks to
|
||||
Ronny Pfannschmidt and Donald Stufft for helping to isolate it.
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ holger krekel
|
|||
- fix issue435: make reload() work when assert rewriting is active.
|
||||
Thanks Daniel Hahler.
|
||||
|
||||
- fix issue616: conftest.py files and their contained fixutres are now
|
||||
- fix issue616: conftest.py files and their contained fixtures are now
|
||||
properly considered for visibility, independently from the exact
|
||||
current working directory and test arguments that are used.
|
||||
Many thanks to Eric Siegerman and his PR235 which contains
|
||||
|
|
|
|||
|
|
@ -5343,7 +5343,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
|||
Thanks Ronny Pfannschmidt for most of the merging work.
|
||||
|
||||
- "-r" option now accepts "a" to include all possible reports, similar
|
||||
to passing "fEsxXw" explicitly (isse960).
|
||||
to passing "fEsxXw" explicitly (issue960).
|
||||
Thanks Abhijeet Kasurde for the PR.
|
||||
|
||||
- avoid python3.5 deprecation warnings by introducing version
|
||||
|
|
@ -5633,7 +5633,7 @@ time or change existing behaviors in order to make them less surprising/more use
|
|||
- fix issue435: make reload() work when assert rewriting is active.
|
||||
Thanks Daniel Hahler.
|
||||
|
||||
- fix issue616: conftest.py files and their contained fixutres are now
|
||||
- fix issue616: conftest.py files and their contained fixtures are now
|
||||
properly considered for visibility, independently from the exact
|
||||
current working directory and test arguments that are used.
|
||||
Many thanks to Eric Siegerman and his PR235 which contains
|
||||
|
|
@ -7180,7 +7180,7 @@ Bug fixes:
|
|||
|
||||
- streamlined plugin loading: order is now as documented in
|
||||
customize.html: setuptools, ENV, commandline, conftest.
|
||||
also setuptools entry point names are turned to canonical namees ("pytest_*")
|
||||
also setuptools entry point names are turned to canonical names ("pytest_*")
|
||||
|
||||
- automatically skip tests that need 'capfd' but have no os.dup
|
||||
|
||||
|
|
|
|||
|
|
@ -111,7 +111,7 @@ More details can be found in the `original PR <https://github.com/pytest-dev/pyt
|
|||
|
||||
.. note::
|
||||
|
||||
in a future major relase of pytest we will introduce class based markers,
|
||||
in a future major release of pytest we will introduce class based markers,
|
||||
at which point markers will no longer be limited to instances of :py:class:`Mark`.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -92,7 +92,7 @@ It provide tools to raise money and share your finances in full transparency.
|
|||
It is the platform of choice for individuals and companies that want to make one-time or
|
||||
monthly donations directly to the project.
|
||||
|
||||
See more datails in the `pytest collective`_.
|
||||
See more details in the `pytest collective`_.
|
||||
|
||||
.. _Open Collective: https://opencollective.com
|
||||
.. _pytest collective: https://opencollective.com/pytest
|
||||
|
|
|
|||
|
|
@ -28,4 +28,4 @@ be happy to accept those patches and make new ``4.6`` releases **until mid-2020*
|
|||
Technical Aspects
|
||||
-----------------
|
||||
|
||||
The technical aspects of the Python 2.7 and 3.4 support plan (such as when releases will occurr, how to backport fixes, etc) is described in issue `#5275 <https://github.com/pytest-dev/pytest/issues/5275>`__.
|
||||
The technical aspects of the Python 2.7 and 3.4 support plan (such as when releases will occur, how to backport fixes, etc) is described in issue `#5275 <https://github.com/pytest-dev/pytest/issues/5275>`__.
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ It provide tools to raise money and share your finances in full transparency.
|
|||
It is the platform of choice for individuals and companies that want to make one-time or
|
||||
monthly donations directly to the project.
|
||||
|
||||
See more datails in the `pytest collective`_.
|
||||
See more details in the `pytest collective`_.
|
||||
|
||||
|
||||
.. _Tidelift: https://tidelift.com
|
||||
|
|
|
|||
Loading…
Reference in New Issue