-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup CI tests #5
Comments
Will check that out. |
I haven’t set any tests up for CI, but I have used Vader for some of my internal script functions. There are examples in the README. June Gunn has tests in seoul256.vim, gv.vim, vim-after-object, and there’s a wiki page describing it. |
Sounds good! Even a syntax-level check is already better than nothing. |
@hauleth @halostatue who wants to take care of this? Having both vim 8.0 and neovim tested with the CI will help us get the other PRs through. |
I’m not likely to have time for a while, but I mentioned this in reply to a comment from another watcher. |
It would be nice if the changes in the plugin could automatically be tested against multiple version of vim.
/cc @hauleth @halostatue
The text was updated successfully, but these errors were encountered: