doctest

If I run the following command: >python manage.py test Django looks at tests.py in my application, and runs any doctests or unit tests in that file. It also looks at the __ test __ dictionary for extra tests to run. So I can link doctests from other modules like so: #tests.py from myapp.module1 import _function1, _function2 __test__ = { "_function1": _function1, "_function2": _function2 } If I want to include more doctests, is there an easier way than enumerating them all in this dictionary? Ideally, I just want to have Django find all doctests in all modules in the myapp application. Is there

I am trying to get into testing in Python using the doctest module. At the moment I do Write the tests for the functions. implement the functions code. If Tests pass, write more tests and more code. When the function is done move on to the next function to implement. So after 3 or 4 (independent) functions in the same module with many tests I get a huge output by doctest. And it is a little annoysing. Is there a way to tell doctest "don't test functions a() , b() and c() ", so that it runs only the unmarked functions? I only found the doctest.SKIP flag, which is not sufficient for my needs. I

In the PyCharm IDE, if I right-click on a function/method with a doctest, sometimes the right-click menu will give me the option: " Run 'Doctest my_function_name' " and sometimes the right-click menu, instead, only gives the option to run the whole file (NOT as a doctest). What determines when it will give the "run doctest" option and when it will not? Is there a way to force it one way or the other? asherbar Running a module (or the tests in it) in PyCharm is done via a Run Configuration . When you right click a module, PyCharm searches for an existing Run Configuration for that module. If a

Consider the following demo script: # -*- coding: utf-8 -*- from __future__ import division from __future__ import unicode_literals def myDivi(): """ This is a small demo that just returns the output of a divison. >>> myDivi() 0.5 """ return 1/2 def myUnic(): """ This is a small demo that just returns a string. >>> myUnic() 'abc' """ return 'abc' if __name__ == "__main__": import doctest extraglobs = {} doctest.testmod(extraglobs=extraglobs) The doctest passes on Python 3.5, but fails on Python 2.7.9. The strange thing is, the divison test works, but the unicode test fails. I have seen various

Python doctests are cool. Let me start with a simple example: def foo(): """ >>> foo() hello world """ print "hello world" Now let's assume some part is somewhat varying, e.g., because it is a time value or a random number. In general, doctests allow me to specify a wildcard saying using the +ELLIPSIS option. This works fine when for instance "world" is a varying string: def foo(): """ >>> foo() # doctest: +ELLIPSIS hello ... """ print "hello world" In my case however, the variable string is at the beginning of the line: def foo(): """ >>> foo() # doctest: +ELLIPSIS ... world """ print "hello

I have a code base that runs unchanged in Python 2.7 and 3.2+. But the doctests in the documentation rst files are giving me a headache. When I run them in Python2, I get UnicodeEncodeError: 'ascii' codec can't encode character u'\xb2' in position 16: ordinal not in range(128) . If I add .. testsetup:: * from __future__ import unicode_literals then I get a lot of errors like Expected: 'something' Got: u'something' Is there a way to have doctest containing unicode characters in the rst files that work unchanged in Python 2.7 and 3.2+? Make sure you are using Python 3.3. It added the explicit u

I'm trying to keep my source code under the 80 character guideline width that PEP8 recommends, but can't figure out how to wrap my doctest which has results longer than 80 characters. A noddy example: def long_string(): """ Returns a string which is wider than the recommended PEP8 linewidth >>> print long_string() 0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 """ return '0123456789' * 10 I've tried a couple of combinations, including using # doctest: +NORMALIZE_WHITESPACE and trying to simply wrap the line with a newline. Just figured out: