Skip to content

docs: improve wording and hyphenation in non-python tests documentation #14558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dhruvatr wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −2
Open

docs: improve wording and hyphenation in non-python tests documentation #14558

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/en/example/nonpython.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ now execute the test specification:
You get one dot for the passing ``sub1: sub1`` check and one failure.
Obviously in the above ``conftest.py`` you'll want to implement a more
interesting interpretation of the yaml-values. You can easily write
your own domain specific testing language this way.
your own domain-specific testing language this way.

.. note::

Expand Down Expand Up @@ -89,7 +89,7 @@ consulted when reporting in ``verbose`` mode. It should return a tuple
.. regendoc:wipe

While developing your custom test collection and execution it's also
interesting to just look at the collection tree:
interesting to look at the collection tree:

.. code-block:: pytest

Expand Down
Loading