gundo.vim/tests
2010-12-09 22:21:52 -05:00
..
bundled Add a unit test. This here is a grey triangle moment, folks. 2010-11-10 19:52:08 -05:00
vim_test tests: break the undo chain when typing lines 2010-12-09 19:56:33 -05:00
README.markdown Add another unit test. This is so damn painful. 2010-11-12 22:13:22 -05:00
run-tests.sh Add another unit test. This is so damn painful. 2010-11-12 22:13:22 -05:00
test-graph.vim tests: remove unnecessary cpo saving 2010-12-09 19:34:46 -05:00
test-movement.vim tests: fix movement test name 2010-12-09 22:21:52 -05:00
test-toggle.vim tests: remove unnecessary cpo saving 2010-12-09 19:34:46 -05:00
vimrc_test Add a unit test. This here is a grey triangle moment, folks. 2010-11-10 19:52:08 -05:00

This is Gundo's test suite. In case you didn't know, unit testing vim plugins is a horrible experience.

Gundo bundles Luc Hermitte's UT framework to make the process less painful.

To run a test, cd into the tests directory and use:

./run-tests.sh [[some-test.vim] ...]

The script will run the console vim command with its own vimrc and .vim directory, so none of your other plugins should interfere. The result of the tests will be shown in the quickfix window of this vim instance.

The q key will be remapped to perform :qa! so you can close everything quickly if it all looks good.

The run-tests.sh script is still a work in progress. I need to figure out a good way of collecting results. Suggestions and/or patches are very welcome.