Skip to main content

Create and run markdown Readmes from within pytest

Project description

author: gk version: 190910

Generating Markdown - While Testing Contained Claims

Build Status codecovPyPI    version

Table Of Contents

Few things are more annoying than stuff which does not work as announced, especially when you find out only after an invest of time and energy.

Documentation is often prone to produce such situations, since hard to keep 100% in sync with the code evolution.

This is a set of tools, generating documentation, while verifying the documented claims about code behaviour - without the need to adapt the source code, e.g. by modifying doc strings:

When the documentation is using a lot of code examples then a very welcome additional benefit of writing it like shown is the availability of source code autoformatters.

Other Example:

This "" was built into this template, where html comment style placeholders had been replaced while running pytest on test_tutorial.

Lets run a bash command and assert on its results. Note that the command is shown in the readme, incl. result and the result can be asserted upon.

$ cat "/etc/hosts" | grep localhost   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
$ ls "/home/gk/repos/pytest2md/tests"

$ ls -lta /etc/hosts
-rw-r--r--. 1 root root 286 Jul 22 12:08 /etc/hosts

Generated by:

Inline Python Function Execution

via the md_from_source_code function you can write fluent markdown (tested) python combos:

hi = 'hello world'
assert 'world' in hi
print(hi.replace('world', 'joe'))

The functions are evaluated and documented in the order they show up within the textblocks.

Please keep tripple apostrophes - we split the text blocks, searching for those.

State is kept within the outer pytest function, like normally in python. I.e. if you require new state, then start a new pytest function.

Stdout is redirected to an output collector function, i.e. if you print this does result in an "Output" block. If the printout starts with "MARKDOWN:" then we won't wrap that output into fenced code blocks but display as is.

If the string 'breakpoint' occurs in a function body, we won't redirect standardout for displaying output.



ht = p2m.html_table

print(ht([['foo', 'bar'], ['bar', 'baz']], ['h1', 'h2']))
print('As details when summary arg is given:')
t = ht(
    [['joe', 'doe'], ['suzie', 'wong']],
    ['first', 'last'],
    summary='names. click to open...',
assert 'details' in t
assert 'joe</td' in t


$ cat "test_file.json"
    "a": [
            "testfile": "created"
        "Sun Sep 15 21:51:26 2019"
as details
$ cat "test_file.json"
    "a": [
            "testfile": "created"
        "Sun Sep 15 21:51:26 2019"


as link

Generated by:

# if content is given it will create it:
p2m.sh_file(fn, lang='javascript', content=c)
# summary arg creates a details structure:
p2m.sh_file(fn, lang='javascript', content=c, summary='as details')
# creates a link (say True to have the filename as link text)
p2m.sh_file(fn, lang='javascript', content=c, as_link=True)
p2m.sh_file(fn, lang='javascript', content=c, as_link='as link')


$ ./some_command_in_assets arg1 2>&1
/bin/sh: /home/gk/repos/pytest2md/tests/assets/some_command_in_assets: No such file or directory
$ ls -lta | grep total | head -n 1
total 80
$ ls -lta
total 80
-rw-r--r--.  1 gk armynyus  2025 Sep 15 21:51
drwxr-xr-x.  8 gk armynyus  4096 Sep 15 21:51 .git
drwxr-xr-x.  8 gk armynyus  4096 Sep 15 21:50 .
-rw-r--r--.  1 gk armynyus 14039 Sep 15 21:50

...(output truncated - see link below)
$ ls -lta

ls -lta

Generated by:

run = partial(p2m.bash_run, no_cmd_path=True)
# by default we search in assets for the command to run:
# errors have to be redirected:
res = p2m.bash_run('some_command_in_assets arg1 2>&1')
res = run('ls -lta | grep total | head -n 1')
assert 'total' in res[0]['res']
res = run('ls -lta', into_file='bash_run.txt')
assert 'total' in res[0]['res']
# Ending with .html it converts ansi escape colors to html:
# simple link is created.
# (requires pip install ansi2html)
run('ls -lta', into_file='bash_run.html')


Inserted markdown from running python.

Strings in double apos. are rendered, no need to call a render function.

md('Inserted markdown from running python.')
print('From output of running python ')


From output of running python

More markdown

print('From another function')


From another function

Strings can also contain instructions, like this (looked up in p2m.MdInline namespace class)

$ cd /etc; ls -lta | head -n 5
total 2240
drwxr-xr-x. 156 root root     12288 Sep 13 19:32 .
-rw-r--r--.   1 root root        67 Sep 13 19:32 resolv.conf
-rw-r--r--.   1 root root    124464 Sep  9 08:29
drwxr-xr-x.   2 root root      4096 Sep  6 09:58 w3m

Default inline functions:

        for k in dir(pytest2md.MdInline)
        if not k.startswith('_')



Generated by

        def some_test_function():
            Strings in double apos. are rendered, no need to call a render function.

            def func1():
                md('Inserted markdown from running python.')
                print('From output of running python ')

            > More  markdown

            def func2():
                print('From another function')

            Strings can also contain instructions, like this (looked up in p2m.MdInline namespace class)

            <bash: cd /etc; ls -lta | head -n 5>

            Default inline functions:

            def known():
                        for k in dir(pytest2md.MdInline)
                        if not k.startswith('_')


Table of Contents

p2m.write_markdown(with_source_ref=True, make_toc=True)

See this tutorial.

Link Replacements

Technical markdown content wants to link to source code often. How to get those links working and that convenient?

The module does offer also some source finding / link replacement feature, via the mdtool module. The latter link was built simply by this:


Other example: This link was created by replacing "SRC" with the path to a file matching, under a given directory, prefixed by an arbitrary base URL.


These will be replaced:

[title:this,fmatch:test_tutorial,lmatch:line_match] <SRC> (remove space between] and <)

  • title: The link title - text the user reads
  • fmatch: substring match for the link destination file
  • lmatch: Find matching line within that file
  • show_raw: Link to raw version of file, not the one rendered by the repo server
  • path: Fix file path (usually derived by fmach)
  • line: Fix the line number of the link (usually done via lmatch)

Code Repo Hoster Specific Source Links

Github, Gitlab, Bitbucked or Plain directory based static content servers all have their conventional URLs regarding those links.

Since all of these are just serving static content w/o js possibilities, you have to parametrize the intended hoster in your environment, before running a pytest / push cycle. That way the links will be working on the hoster.

Currently we understand the following namespaces for links:

    "github": "",
    "github_raw": "",
    "static": "file://%(d_repo_base)s/%(path)s",
    "static_raw": "file://%(d_repo_base)s/%(path)s"

Setting a link template

  • export MD_LINKS_FOR=github # before running pytest / push
  • <!-- md_links_for: github --> # in the markdown template, static

The latter can be overwritten by environ, should you want to push from time to time to a different code hoster.

Link Refs

We minimize the problem of varying generated target markdown, dependent on the hoster. How? Like any problem in IT is solved.

By building reference links the differences of e.g. a for github vs. gitlab is restricted to the links section on the end of the generated markdown. In the markdown bodies you'll just see link names, which remain the same.

Check the end of the rendering result at the end of this, in order to see the results for the hoster you are reading this markdown file currently.


  • At normal runs of pytest, the link base URL is just a local file:// link,

  • Before pushes one can set via environ (e.g. export MD_LINKS_FOR=github) these e.g. to the github base URL or the repo.

  • [key-values] constructs are supported as well, extending to beyond just the base url. Example following:

Source code showing is done like this:

    def test_sh_code(self):
        md('Source code showing is done like this:')
            '> Is [title:this,fmatch:test_tutorial,lmatch:exotic]<SRC> an exotic form of a recursion? ;-)  '

Is this an exotic form of a recursion? ;-)

*Auto generated by pytest2md, running ./tests/


  • Local Renderer:

    pip install grip

to get a local github compliant markdown renderer, reloading after changes of the generated markdown.

  • Using fixtures with unittest style test classes

Create a like:

root@localhost tests]# cat
import pytest
import pytest2md as p2m

def write_md(request):
    def fin():
        request.cls.p2m.write_markdown(with_source_ref=True, make_toc=False)


then use like:

class TestDevUsage(unittest.TestCase):
    p2m = p2m # on module level: p2m.P2M(__file__, fn_target_md='')



None. If you would screw up your host running pytest normally, then you will get the same result, when running markdown generating tests.

Here is a bigger tutorial, from pytest2md.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pytest2md-190910.tar.gz (38.8 kB view hashes)

Uploaded Source

Built Distribution

pytest2md-190910-py3-none-any.whl (33.7 kB view hashes)

Uploaded Python 3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page