##// END OF EJS Templates
upstream » ipython
RSS

Clone from https://github.com/ipython/ipython.git

Make our temp file mixin unittest-friendly....
Make our temp file mixin unittest-friendly. This does not break any nose compatibility, but it lets us use our mixin with normal unittest.TestCase objects in addition to nose-oriented tests. We're trying to lower our dependency on specifics of the nose api, so that in the future we might be able to run without nose at all (as unittest improves).
Fernando Perez - - Load All Authors

File last commit:

r1334:049617d6
r2907:566a32b3
Show More
test_exampleip.txt
30 lines | 816 B | text/plain | TextLexer
/ IPython / testing / plugin / test_exampleip.txt
History | Annotation | Raw |Copy content |Copy permalink
=================================
Tests in example form - IPython
=================================
You can write text files with examples that use IPython prompts (as long as you
use the nose ipython doctest plugin), but you can not mix and match prompt
styles in a single file. That is, you either use all ``>>>`` prompts or all
IPython-style prompts. Your test suite *can* have both types, you just need to
put each type of example in a separate. Using IPython prompts, you can paste
directly from your session::
In [5]: s="Hello World"
In [6]: s.upper()
Out[6]: 'HELLO WORLD'
Another example::
In [8]: 1+3
Out[8]: 4
Just like in IPython docstrings, you can use all IPython syntax and features::
In [9]: !echo "hello"
hello
In [10]: a='hi'
In [11]: !echo $a
hi