[TIP] towards 1.0 / code URLS using py.test?

[Pete Forman]

holger krekel <holger at merlinux.de> writes:

 > Feel free to also mail me your favourite annoyance or feature wish

I'd like to automagically run doctests within py.test.  I understand
that text files can be so processed.  What I currently use is this
form of manually maintained test file:

import doctest
# todo: test independently without importing all at once
import foo, test_bar, baz

def test_foo():
    assert doctest.testmod(foo)[0] == 0

def test_bar2():
    assert doctest.testmod(test_bar)[0] == 0

def test_baz():
    assert doctest.testmod(baz)[0] == 0

if __name__ == "__main__":
    test_foo()
    test_bar2()
    test_baz()


The way that I like to work is to use both doctest and py.test.
Doctest cases are simple examples to illustrate to users what my code
is doing.  py.test cases are more comprehensive covering edge cases,
etc.  What is missing OOTB is for py.test to run doctests in addition
to the comprehensive tests.
-- 
Pete Forman                -./\.-  Disclaimer: This post is originated
WesternGeco                  -./\.-   by myself and does not represent
pete.forman at westerngeco.com    -./\.-   the opinion of Schlumberger or
http://petef.port5.com           -./\.-   WesternGeco.