(Clarifications. TT font on options and file names. Using the after directory.) |
JohnBeckett (talk | contribs) (minor format and move abbreviations to comments) |
||
Line 12: | Line 12: | ||
|category3=Python |
|category3=Python |
||
}} |
}} |
||
− | Vim has a wonderful ability to integrate with external tools, like compilers, make, ctags, etc. That's one of the reasons we love it. PyUnit can be seen as a "compiler" for Python code. |
+ | Vim has a wonderful ability to integrate with external tools, like compilers, make, ctags, etc. That's one of the reasons we love it. PyUnit can be seen as a "compiler" for Python code. |
Doing |
Doing |
||
− | |||
<pre> |
<pre> |
||
:compiler pyunit |
:compiler pyunit |
||
Line 23: | Line 22: | ||
To run all your unit tests at once, using Vim's <tt>:make</tt> command, you'll need to set the <tt>'makeprg'</tt> option and provide a test runner. This is often done using an <tt>alltests.py</tt> script. |
To run all your unit tests at once, using Vim's <tt>:make</tt> command, you'll need to set the <tt>'makeprg'</tt> option and provide a test runner. This is often done using an <tt>alltests.py</tt> script. |
||
− | |||
<pre> |
<pre> |
||
:setlocal makeprg=./alltests.py |
:setlocal makeprg=./alltests.py |
||
Line 64: | Line 62: | ||
# |
# |
||
# Place this file somewhere where it can be run, such as ${HOME}/bin/alltests.py |
# Place this file somewhere where it can be run, such as ${HOME}/bin/alltests.py |
||
− | # |
||
import unittest, sys, os, re |
import unittest, sys, os, re |
||
def find_all_test_files(): |
def find_all_test_files(): |
||
− | + | t_py_re = re.compile('^t(est)?_.*\.py$') |
|
− | + | is_test = lambda filename: t_py_re.match(filename) |
|
− | + | drop_dot_py = lambda filename: filename[:-3] |
|
− | + | return [drop_dot_py(module) for module in filter(is_test, os.listdir(os.curdir))] |
|
− | |||
def suite(): |
def suite(): |
||
− | + | sys.path.append(os.curdir) |
|
+ | modules_to_test = find_all_test_files() |
||
− | |||
− | + | print 'Testing', ', '.join(modules_to_test) |
|
+ | alltests = unittest.TestSuite() |
||
− | print 'Testing', ', '.join(modules_to_test) |
||
⚫ | |||
− | |||
− | + | alltests.addTest(unittest.findTestCases(module)) |
|
⚫ | |||
⚫ | |||
− | alltests.addTest(unittest.findTestCases(module)) |
||
− | |||
⚫ | |||
if __name__ == '__main__': |
if __name__ == '__main__': |
||
− | + | unittest.main(defaultTest='suite') |
|
− | |||
</pre> |
</pre> |
||
Line 95: | Line 87: | ||
<pre> |
<pre> |
||
− | " Additions to Vim's filetype plugin for Python, to set up PyUnit as |
+ | " Additions to Vim's filetype plugin for Python, to set up PyUnit as |
− | " 'compiler' for Python files. |
+ | " the 'compiler' for Python files. |
− | " |
+ | " Set the errorformat. |
compiler pyunit |
compiler pyunit |
||
− | " Set |
+ | " Set 'makeprg': this allows you to call :make on any .py file and |
− | " of the unit tests in the current working directory |
+ | " run all of the unit tests in the current working directory. |
− | " Ensure you have this file |
+ | " Ensure you have this file. |
setlocal makeprg=${HOME}/bin/alltests.py |
setlocal makeprg=${HOME}/bin/alltests.py |
||
− | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
</pre> |
</pre> |
||
==References== |
==References== |
||
− | |||
*{{help|'efm'}} |
*{{help|'efm'}} |
||
*{{help|'makeprg'}} |
*{{help|'makeprg'}} |
||
Line 124: | Line 107: | ||
==Comments== |
==Comments== |
||
⚫ | |||
+ | <pre> |
||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
+ | </pre> |
||
+ | |||
+ | ---- |
||
I don't think the abbreviations belong in this tip. They are not ''on topic'' and may be distracting. ([[User:Spiiph|Spiiph]] 10:48, 3 August 2009 (UTC)) |
I don't think the abbreviations belong in this tip. They are not ''on topic'' and may be distracting. ([[User:Spiiph|Spiiph]] 10:48, 3 August 2009 (UTC)) |
||
+ | |||
+ | There are no tips really suitable for holding the iabbr info; following are slightly plausible candidates. Meanwhile, I have moved the abbreviations to the comments section where they are less intrusive. [[User:JohnBeckett|JohnBeckett]] 03:20, 4 August 2009 (UTC) |
||
+ | *[[VimTip610|610 Use abbreviations for frequently-used words]] |
||
+ | *[[VimTip709|709 Simple creation of scripts]] |
||
+ | *[[VimTip778|778 Speed up Python coding]] |
||
+ | *[[VimTip1041|1041 Snippets for JavaScript, HTML and Python]] |
Revision as of 03:20, 4 August 2009
created July 10, 2002 · complexity intermediate · author Stefan Roemer, Max Ischenko · version 6.2
Vim has a wonderful ability to integrate with external tools, like compilers, make, ctags, etc. That's one of the reasons we love it. PyUnit can be seen as a "compiler" for Python code.
Doing
:compiler pyunit
will set the 'errorformat' option for PyUnit, enabling Vim to parse a unittest test runner's output and to enter quickfix mode.
To run all your unit tests at once, using Vim's :make command, you'll need to set the 'makeprg' option and provide a test runner. This is often done using an alltests.py script.
:setlocal makeprg=./alltests.py
Here is an example alltests.py:
#!/usr/bin/env python2 import unittest import sys sys.path.append('unittests') modules_to_test = ( 'fooTest', 'barTest', 'bazTest', ) def suite(): alltests = unittest.TestSuite() for module in map(__import__, modules_to_test): alltests.addTest(unittest.findTestCases(module)) return alltests if __name__ == '__main__': unittest.main(defaultTest='suite')
Here is an alternative alltests.py:
#!/usr/bin/env python # # This script is based on the one found at http://vim.wikia.com/wiki/VimTip280 # but has been generalised. It searches the current working directory for # t_*.py or test_*.py files and runs each of the unit-tests found within. # # When run from within Vim as its 'makeprg' with the correct 'errorformat' set, # any failure will deliver your cursor to the first line that breaks the unit # tests. # # Place this file somewhere where it can be run, such as ${HOME}/bin/alltests.py import unittest, sys, os, re def find_all_test_files(): t_py_re = re.compile('^t(est)?_.*\.py$') is_test = lambda filename: t_py_re.match(filename) drop_dot_py = lambda filename: filename[:-3] return [drop_dot_py(module) for module in filter(is_test, os.listdir(os.curdir))] def suite(): sys.path.append(os.curdir) modules_to_test = find_all_test_files() print 'Testing', ', '.join(modules_to_test) alltests = unittest.TestSuite() for module in map(__import__, modules_to_test): alltests.addTest(unittest.findTestCases(module)) return alltests if __name__ == '__main__': unittest.main(defaultTest='suite')
To have Vim automatically use these settings for all Python files, add the following to ~/.vim/after/ftplugin/python.vim ($HOME\vimfiles\after\ftplugin\python.vim on Windows)
" Additions to Vim's filetype plugin for Python, to set up PyUnit as " the 'compiler' for Python files. " Set the errorformat. compiler pyunit " Set 'makeprg': this allows you to call :make on any .py file and " run all of the unit tests in the current working directory. " Ensure you have this file. setlocal makeprg=${HOME}/bin/alltests.py
References
Comments
The following abbreviations are useful when writing unit tests in Python.
iabbr <buffer> sa_ self.assert_ iabbr <buffer> sae self.assertEquals iabbr <buffer> saf self.assertFalse iabbr <buffer> san self.assertNotEquals iabbr <buffer> sar self.assertRaises iabbr <buffer> sat self.assertTrue
I don't think the abbreviations belong in this tip. They are not on topic and may be distracting. (Spiiph 10:48, 3 August 2009 (UTC))
There are no tips really suitable for holding the iabbr info; following are slightly plausible candidates. Meanwhile, I have moved the abbreviations to the comments section where they are less intrusive. JohnBeckett 03:20, 4 August 2009 (UTC)