-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup testing environment #619
Comments
ping @VundleVim/team |
👍 sounds good. willing to help out with this specific item in bits and pieces 😄 |
@VundleVim/team not sure how far you are on this but just in case here are some links that I found:
Probably most of these you are already aware of but just in case 😏 |
Nice @ryanoasis ! I should have something preliminary going soon, and we can discuss from there! |
@silfverstrom awesome sounds good 👍 |
@ryanoasis wow, that's a lot of stuff to go through :) 👍 |
So do we have a TravisCI account? |
@btreeinfinity not that I know of, but it's an easy fix when we have a clear testing structure in place. |
@btreeinfinity no, there's no account for vunlde! |
just wondering if there is any status on this? |
@nfischer looks interesting |
Just requested access to this Organization for Travis CI |
@VundleVim/team FYI, just starting messing around with this here: https://travis-ci.org/ryanoasis/Vundle.vim |
@ryanoasis Vader? Good pick! |
I just wanted to get started at least and I didn't compare very in depth but Vader seemed to be fairly active and popular compared to the other options. I will have to take a look at vroom, I think it is safe to cross off @nfischer do you have any specific examples on vroom? I did see on the readme a sample Travis CI config. |
@nfischer thanks I'll try it out 👍 |
I think I liked vader the best so far. I really need to get back into this because it will provide a safety net for at least the basic functionality. I do plan on testing and merging some the more recent PRs but after that I think I'll shift focus to testing. I don't want to be the one responsible for breaking vundle! 🙊 |
I think maybe it's time to get back to looking into this so we can get back to at least considering features 😄 |
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.
The text was updated successfully, but these errors were encountered: