Hi, > Anything we can do to make it easier for plugin authors? A big > improvement would be if plugins would write tests that we can run > against different Vim configurations. I haven't seen plugins with > tests though...
There are a few plugins doing automated tests. And of course, each has taken a different path. For instance, I have a few plugins with automated tests. See for instance lh-cpp: https://github.com/LucHermitte/lh-cpp which has both unit tests that can fill quickfix window and more elaborated tests where I check what the buffer contains after the commands I execute. https://github.com/kana/vim-vspec provides another framework for testing plugins. My biggest issue is related to feedkey() that I wasn't able to use through --remote-expr to trigger omni-completion. I had to find other way to test my snippets. Regards -- Luc Hermitte -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
