Skip to content

[WIP] Integration tests: Docker, tmux, Neovim - #124

Open
blueyed wants to merge 19 commits into
junegunn:masterfrom
blueyed:integration-tests
Open

blueyed wants to merge 19 commits into
junegunn:masterfrom
blueyed:integration-tests

Conversation

@blueyed

@blueyed blueyed commented Mar 11, 2017 •

Copy link
Copy Markdown
Collaborator

Includes #123 and #107.

It is based on Neomake's tests, and the tmux part inspired by vim-diminactive's tests.

This uses a Docker image (currently blueyed/vader.vim, based on vim-testbed), and runs the test in there.

This improves the overall build time, since Vim does not have to be compiled, and tests against different Vim version.

I have also added neovim to the build matrix.

Vim 7.3 currently fails since Ruby is not installed therein (will be fixed with Vimjas/vim-testbed#23 / Vimjas/vim-testbed#9).

@blueyed blueyed changed the title Integration tests: Docker, tmux, Neovim [WIP] Integration tests: Docker, tmux, Neovim Apr 2, 2017
@blueyed blueyed mentioned this pull request Apr 2, 2017
2 tasks
blueyed added 19 commits April 21, 2017 13:22
This wraps the temporary script into a function to get the line number
of `vader#assert` calls.
E.g.

    ( 1/13) [EXECUTE] (X) Vim(finish):E168: :finish used outside of a sourced file
      > /home/user/src/neomake/tests/utils.vader:11: finish  " foo

Also passes it through to `s:execute`.
This will use the actual file name for included lines.

Fixes junegunn#88.
Wrapping the code in a function will cause them to not be available otherwise,
or g:SyntaxAt() would have to be used.
While this means more overhead in general, it allows to access
script-local variables in the tests.

squash! FEAT: move s:prepare into vader#window#execute

Use `vader#log` directly instead of `:Log`, since the latter might not
be defined (yet).
This uses a Docker image (currently blueyed/vader.vim, based on
vim-testbed), and runs the test in there.

This improves the overall build time, since Vim does not have to be
compiled, and tests against different Vim version.

I have also added neovim to the build matrix.

Vim 7.3 currently fails since Ruby is not installed therein.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant