Re: Advice needed: best practices for vim plugin testing

Hi everyone, Thanks for all the valuable suggestions. The method I found out to be the most suitable, dependecy free and sane (this is highly personal) was to write bash tests which in turn invokes vim with a given number of flags and which sources a given script which ends with either "qall!"

Re: Advice needed: best practices for vim plugin testing

On 19/10/2017 23:36, Marcin Szamotulski wrote: On 11:10 Thu 19 Oct , Felipe Vieira wrote: 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. > >

Re: Advice needed: best practices for vim plugin testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey all, thanks for all of your replies. I will dutifully check those soon! With so many options I feel like I was not looking at the right places. I shall give a feedback on those in a couple of weeks. Best, - -- Felipe Martins Vieira I have

Re: Advice needed: best practices for vim plugin testing

Felipe Vieira wrote: > 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

Re: Advice needed: best practices for vim plugin testing

On 10:10 Fri 20 Oct , Luc Hermitte wrote: > 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

Re: Advice needed: best practices for vim plugin testing

2017/10/20 16:29 "lith" : > I have tried a couple of other vim plugins for testing with little/no success. Which one did you try? Are you looking for something like vader < https://github.com/junegunn/vader.vim>? Or if you want a full stack one, themis.vim is also the

Re: Advice needed: best practices for vim plugin testing

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,

Re: Advice needed: best practices for vim plugin testing

> I have tried a couple of other vim plugins for testing with little/no success. Which one did you try? Are you looking for something like vader ? Regards -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply

Re: Advice needed: best practices for vim plugin testing

On 23:49 Thu 19 Oct , Felipe M. Vieira wrote: > On Thu, October 19, 2017 at 23:36, Marcin Szamotulski wrote: > > On 11:10 Thu 19 Oct , Felipe Vieira wrote: > > > Hi everyone, > > > > > > I've been trying to develop a plugin and I'm used to writing testing for > > > the > > > softwares I

Re: Advice needed: best practices for vim plugin testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, October 19, 2017 at 23:36, Marcin Szamotulski wrote: > On 11:10 Thu 19 Oct , Felipe Vieira wrote: > > Hi everyone, > > > > I've been trying to develop a plugin and I'm used to writing testing for the > > softwares I develop. The problem

Re: Advice needed: best practices for vim plugin testing

On 11:10 Thu 19 Oct , Felipe Vieira wrote: > 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 >

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