Setup testing environment

[silfverstrom]

Vundle should have a set of automated tests, and a clear structure of adding new tests alongside a issue/pull request.

The tests could also be integrated towards TravisCI, which makes it easier to spot pull requests with broken tests.

I'm looking into how to best achieve this, lets keep a discussion in this thread.

[silfverstrom]

ping @VundleVim/team

[ryanoasis]

👍 sounds good. willing to help out with this specific item in bits and pieces 😄

[ryanoasis]

@VundleVim/team not sure how far you are on this but just in case here are some links that I found:

• http://whileimautomaton.net/2013/02/08211255
• http://whileimautomaton.net/2013/02/13211500
• http://mudge.name/2012/04/18/testing-vim-plugins-on-travis-ci-with-rspec-and-vimrunner.html
• http://vimcasts.org/episodes/an-introduction-to-vspec/
• http://hashrocket.com/blog/posts/vimscript-and-you
• http://lanyrd.com/2013/testing-vimscript/coverage/
• https://github.com/kana/vim-vspec
• https://github.com/thinca/vim-themis
• https://github.com/junegunn/vader.vim
• https://github.com/AndrewRadev/vimrunner
• https://github.com/mivok/vimcram
• https://github.com/syngan/vim-vimlint
• https://github.com/ynkdir/vim-vimlparser

Probably most of these you are already aware of but just in case 😏

[silfverstrom]

Nice @ryanoasis ! I should have something preliminary going soon, and we can discuss from there!

[ryanoasis]

@silfverstrom awesome sounds good 👍

[gmarik]

@ryanoasis wow, that's a lot of stuff to go through :) 👍

[opsroller]

So do we have a TravisCI account?

[silfverstrom]

@btreeinfinity not that I know of, but it's an easy fix when we have a clear testing structure in place.

[gmarik]

@btreeinfinity no, there's no account for vunlde!

[ryanoasis]

just wondering if there is any status on this?