gundo.vim / tests / README.markdown

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.

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.