Thursday, October 19, 2017

Advice needed: best practices for vim plugin testing

Hi everyone,

I've been trying to develop a plugin and I'm used to writing testing for the
softwares I develop. The problem is that I cannot find a suitable testing
platform for vim plugins. This makes me feel uncomfortable in pushing
improvements made on my own fork of a bigger project (this may adversely impact
hundreds of users, and I think the codebase is complex enough; tests would
force some adherence to what is already coded and improve the plugin itself).

I have tried a couple of other vim plugins for testing with little/no success.

**What currently is the best practice for developing vim plugins?**
(preferably an official vim testing platform for plugins)

It is needless to say how important is to develop tests for software (this is
beyond the point here).

I don't thinks this information is very relevant but:

* I have some experience with vimscript
* I program in python most of the time
* The plugin is: https://github.com/python-mode/python-mode (my own fork:
https://github.com/fmv1992/python-mode)
* I am willing to learn whatever it takes to be able to develop testing for my
plugin (as long as it is something 'official/stable')

Best,

Felipe.

--
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments: