History

Rane Brown 45025fa4f0 Fix docker build command syntax. Closes #736 .		2019-08-01 05:19:39 -06:00
..
resources	Rename folder	2019-07-13 21:50:35 -06:00
vader_includes	Move helper files so they don't get run with test/*	2019-07-20 22:12:07 -06:00
link_creation.vader	Move helper files so they don't get run with test/*	2019-07-20 22:12:07 -06:00
Readme.md	Fix docker build command syntax. Closes #736 .	2019-08-01 05:19:39 -06:00
run_tests.sh	Update test script and documentation.	2019-07-24 21:57:01 -06:00
tabnext_delay.vader	Move helper files so they don't get run with test/*	2019-07-20 22:12:07 -06:00
vimrc	Fix paths and add some additional settings	2019-07-14 21:50:49 -06:00

Readme.md

Vimwiki Tests

This directory contains a test framework used to automatically test/verify Vimwiki functionality. It is based on the following tools:

Resources

Vim patches
Example test cases:

Building Docker Image

To build the Docker image run docker build -t vimwiki . from the Vimwiki repository root (same location as the Dockerfile).

Running Tests

Manual Steps

Starting in the test directory run this command:

docker run -it --rm -v $PWD/../:/testplugin -v $PWD/../test:/home vimwiki vim_7.4.1099 -u test/vimrc -i NONE

This will open a vim instance in the docker container and then all tests can be run with :Vader test/* or individual tests can be run.

Note: Substitute vim_7.4.1099 for any of the vim versions in the Dockerfile.

Automated Tests

The script in the test/ directory named run_test.sh can be used to automatically run all tests for all installed vim versions. The vim/nvim versions are parsed from the Dockerfile. This script will also run Vint for all plugin source files. For more information run ./run_tests.sh -h.

Known Issues

neovim v0.2.x does not work correctly with Vader output from the docker container. No test results are printed and an error message saying Vim: Error reading input, exiting...
- Probably need to look into this more and determine if the issue is Vader, Neovim, or Docker.