1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382
|
Restructured Text Parsers
=========================
Sybil includes a range of parsers for extracting and checking examples from
Restructured Text including the ability to :ref:`capture <capture-parser>` previous blocks into a
variable in the :attr:`~sybil.Document.namespace`, and :ref:`skip <skip-parser>` the evaluation of
examples where necessary.
.. _doctest-parser:
doctest
-------
Parsers are included for both classic :ref:`doctest <doctest-simple-testfile>` examples
along with those in :rst:dir:`doctest` directives.
They are evaluated in the document's :attr:`~sybil.Document.namespace`.
The parsers can optionally be instantiated with
:ref:`doctest option flags<option-flags-and-directives>`.
Here are some classic :ref:`doctest <doctest-simple-testfile>` examples:
.. literalinclude:: examples/rest/doctest.rst
:language: rest
These could be parsed with the a :class:`sybil.parsers.rest.DocTestParser` in the
following configuration:
.. code-block:: python
from sybil import Sybil
from sybil.parsers.rest import DocTestParser
sybil = Sybil(parsers=[DocTestParser()])
.. invisible-code-block: python
from tests.helpers import check_path
check_path('examples/rest/doctest.rst', sybil, expected=3)
If you want to ensure that only examples within a :rst:dir:`doctest` directive are checked,
and any other doctest examples are ignored, then you can use the
:class:`sybil.parsers.rest.DocTestDirectiveParser` instead:
.. literalinclude:: examples/rest/doctest-directive.rst
:language: rest
These could be checked with the following configuration:
.. code-block:: python
from sybil import Sybil
from sybil.parsers.rest import DocTestDirectiveParser
sybil = Sybil(parsers=[DocTestDirectiveParser()])
.. invisible-code-block: python
from tests.helpers import check_path
check_path('examples/rest/doctest-directive.rst', sybil, expected=1)
.. note::
You will have to enable :external+sphinx:doc:`sphinx.ext.doctest <usage/extensions/doctest>`
in your ``conf.py`` for Sphinx to render :rst:dir:`doctest` directives.
A :data:`~sybil.evaluators.doctest.NUMBER` option flag is provided such that floating point
numbers can be used in examples without worrying about precision errors. An example
such as the following can be problematic:
.. literalinclude:: examples/rest/number.rst
:language: rest
However, it can be checked with the following configuration:
.. code-block:: python
from sybil import Sybil
from sybil.parsers.rest import DocTestParser
from sybil.evaluators.doctest import NUMBER
sybil = Sybil(parsers=[DocTestParser(optionflags=NUMBER)])
.. invisible-code-block: python
from tests.helpers import check_path
check_path('examples/rest/number.rst', sybil, expected=2)
.. _codeblock-parser:
Code blocks
-----------
The codeblock parsers extract examples from Sphinx :rst:dir:`code-block`
directives and evaluate them in the document's :attr:`~sybil.Document.namespace`.
The boilerplate necessary for examples to successfully evaluate and be checked
can hinder the quality of documentation.
To help with this, these parsers also evaluate "invisible" code blocks such as this one:
.. literalinclude:: examples/quickstart/example.rst
:language: rest
:lines: 5-9
These take advantage of Sphinx `comment`__ syntax so that the code block will
not be rendered in your documentation but can be used to set up the document's
namespace or make assertions about what the evaluation of other examples has
put in that namespace.
__ http://www.sphinx-doc.org/en/stable/rest.html#comments
Python
~~~~~~
Python code blocks can be checked using the :class:`sybil.parsers.rest.PythonCodeBlockParser`.
Here's a Python code block and an invisible Python code block that checks it:
.. literalinclude:: examples/rest/codeblock-python.rst
:language: rest
These could be checked with the following configuration:
.. code-block:: python
from sybil import Sybil
from sybil.parsers.rest import PythonCodeBlockParser
sybil = Sybil(parsers=[PythonCodeBlockParser()])
.. invisible-code-block: python
from tests.helpers import check_path
check_path('examples/rest/codeblock-python.rst', sybil, expected=2)
.. note::
You should not wrap doctest examples in a ``python`` :rst:dir:`code-block`,
they will render correctly without that and you should use the :ref:`doctest-parser`
parser to check them.
.. _codeblock-other:
Other languages
~~~~~~~~~~~~~~~
.. note::
If your :rst:dir:`code-block` examples define content, such as JSON or YAML, rather than
executable code, you may find the :ref:`capture <capture-parser>` parser is more useful.
:class:`sybil.parsers.rest.CodeBlockParser` can be used to check examples in any language
you require, either by instantiating with a specified language and evaluator, or by subclassing
to create your own parser.
As an example, let's look at evaluating bash commands in a subprocess and checking the output is
as expected::
.. code-block:: bash
$ echo hi there
hi there
.. -> bash_document_text
We can do this using :class:`~sybil.parsers.rest.CodeBlockParser` as follows:
.. code-block:: python
from subprocess import check_output
from textwrap import dedent
from sybil import Sybil
from sybil.parsers.codeblock import CodeBlockParser
def evaluate_bash(example):
command, expected = dedent(example.parsed).strip().split('\n')
actual = check_output(command[2:].split()).strip().decode('ascii')
assert actual == expected, repr(actual) + ' != ' + repr(expected)
parser = CodeBlockParser(language='bash', evaluator=evaluate_bash)
sybil = Sybil(parsers=[parser])
.. invisible-code-block: python
from tests.helpers import check_text
check_text(bash_document_text, sybil)
Alternatively, we can create our own parser class and use it as follows:
.. code-block:: python
from subprocess import check_output
from textwrap import dedent
from sybil import Sybil
from sybil.parsers.codeblock import CodeBlockParser
class BashCodeBlockParser(CodeBlockParser):
language = 'bash'
def evaluate(self, example):
command, expected = dedent(example.parsed).strip().split('\n')
actual = check_output(command[2:].split()).strip().decode('ascii')
assert actual == expected, repr(actual) + ' != ' + repr(expected)
sybil = Sybil([BashCodeBlockParser()])
.. invisible-code-block: python
from tests.helpers import check_text
check_text(bash_document_text, sybil)
.. _capture-parser:
Capturing blocks
----------------
:func:`sybil.parsers.rest.CaptureParser` takes advantage of Sphinx `comment`__ syntax to introduce
a special comment that takes the preceding ReST `block`__ and inserts its
raw content into the document's :attr:`~sybil.Document.namespace`
using the name specified.
__ http://www.sphinx-doc.org/en/stable/rest.html#comments
__ http://www.sphinx-doc.org/en/stable/rest.html?highlight=block#source-code
For example::
A simple example::
root.txt
subdir/
subdir/file.txt
subdir/logs/
.. -> expected_listing
.. --> capture_example
This listing could be captured into the :attr:`~sybil.Document.namespace` using the following
configuration:
.. code-block:: python
from sybil import Sybil
from sybil.parsers.rest import CaptureParser
sybil = Sybil(parsers=[CaptureParser()])
.. invisible-code-block: python
document = check_text(capture_example, sybil)
expected_listing = document.namespace['expected_listing']
The above documentation source, when parsed by this parser and then evaluated,
would mean that ``expected_listing`` could be used in other examples in the
document:
>>> expected_listing.split()
['root.txt', 'subdir/', 'subdir/file.txt', 'subdir/logs/']
It can also be used with :rst:dir:`code-block` examples that define content rather
executable code, for example:
::
.. code-block:: json
{
"a key": "value",
"b key": 42
}
.. -> json_source
.. --> capture_example
.. invisible-code-block: python
document = check_text(capture_example, sybil)
json_source = document.namespace['json_source']
The JSON source can now be used as follows:
>>> import json
>>> json.loads(json_source)
{'a key': 'value', 'b key': 42}
.. note::
It's important that the capture directive, ``.. -> json_source`` in this case, has identical
indentation to the code block above it for this to work.
.. _skip-parser:
Skipping examples
-----------------
:class:`sybil.parsers.rest.SkipParser` takes advantage of Sphinx `comment`__ syntax to introduce
special comments that allow other examples in the document to be skipped.
This can be useful if they include pseudo code or examples that can only be
evaluated on a particular version of Python.
__ https://www.sphinx-doc.org/en/stable/rest.html#comments
For example:
.. literalinclude:: examples/rest/skip.rst
:language: rest
:lines: 1-6
If you need to skip a collection of examples, this can be done as follows:
.. literalinclude:: examples/rest/skip.rst
:language: rest
:lines: 8-15
You can also add conditions to either ``next`` or ``start`` as shown below:
.. literalinclude:: examples/rest/skip.rst
:language: rest
:lines: 17-24
As you can see, any names used in the expression passed to ``if`` must be
present in the document's :attr:`~sybil.Document.namespace`.
:ref:`invisible code blocks <codeblock-parser>`, :class:`setup <sybil.Sybil>`
methods or :ref:`fixtures <pytest_integration>` are good ways to provide these.
When a condition is used to skip one or more following example, it will be reported as a
skipped test in your test runner.
If you wish to have unconditional skips show up as skipped tests, this can be done as follows:
.. literalinclude:: examples/rest/skip.rst
:language: rest
:lines: 26-31
This can also be done when skipping collections of examples:
.. literalinclude:: examples/rest/skip.rst
:language: rest
:lines: 33-40
The above examples could be checked with the following configuration:
.. code-block:: python
from sybil import Sybil
from sybil.parsers.rest import DocTestParser, SkipParser
sybil = Sybil(parsers=[DocTestParser(), SkipParser()])
.. invisible-code-block: python
from tests.helpers import check_path
check_path(
'examples/rest/skip.rst',
sybil,
expected=15,
expected_skips=('not yet working', 'Fix in v5', 'Fix in v5'),
)
.. _clear-namespace:
Clearing the namespace
----------------------
If you want to isolate the testing of your examples within a single source file, you may want
to clear the :class:`~sybil.Document.namespace`. This can be done as follows:
.. literalinclude:: examples/rest/clear.rst
:language: rest
The following configuration is required:
.. code-block:: python
from sybil import Sybil
from sybil.parsers.rest import DocTestParser, ClearNamespaceParser
sybil = Sybil(parsers=[DocTestParser(), ClearNamespaceParser()])
.. invisible-code-block: python
from tests.helpers import check_path
check_path('examples/rest/clear.rst', sybil, expected=4)
|