Hi, > However my concerns are broader as I'm trying to figure out ways of > having a > vim project maintained by different people but enforcing that their > coding > standards/modifications adhere to a test framework.
So, you're not looking for unit testing as there exists quite a few projects, but for linters it seems like vint https://github.com/Kuniwak/vint I've even seen an external tool for github (1) that automatically tries to execute the linter on code pushed -- alas I can't remember the name, or did it stop supporting vim, I can't tell. Anyway, I usually just unit-test my plugin with a mixture of my vim-UT (1) and of vimrunner (3) that I've even registered in travis-ci which gives me little nice badges (4). (1) https://github.com/marketplace (2) https://github.com/LucHermitte/vim-UT/ (3) https://github.com/LucHermitte/vim-UT/blob/master/doc/rspec-integration.md (4) https://github.com/LucHermitte/lh-vim-lib#lh-vim-lib-v400--- -- Luc Hermitte -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
