Don't "bundle exec" with test-kitchen. I think that's where the gap exists here.

This message was sent from my mobile device. 

I apologize in advance for any typographical errors or autocorrections.

> On Jul 22, 2013, at 6:09 PM, "Scott M. Likens" <notifications@github.com> wrote:
> 
> In Gemfile:
> 
> > @@ -5,4 +5,14 @@ group :test do
> >    gem 'rake'
> >    gem 'rspec'
> >    gem 'foodcritic'
> > +  gem 'vagrant-wrapper'
> > +end
> > +
> > +group :integration do
> > +  gem 'test-kitchen', :git => "git://github.com/opscode/test-kitchen.git"
> > +  gem 'berkshelf'
> > +  gem 'rake'
> > +  gem 'kitchen-vagrant', :git => "git://github.com/opscode/kitchen-vagrant.git"
> > +  gem 'kitchen-ec2', :git => "git://github.com/opscode/kitchen-ec2.git"
> > +  gem 'kitchen-lxc', :git => "https://github.com/portertech/kitchen-lxc.git", :tag => 'v0.0.1.beta2'
> @sethvargo sounds like a user experience problem then. As a Bundler user the typical pattern for adding additional drivers is this. (As you know)
> 
> git clone
> emacs Gemfile # add gems to support the drivers you want
> bundle install
> bundle exec kitchen test
> I wish it was as simple as a clone and running with the drivers you want without having to get your hands dirty.
> 
> Not using Bundler helps, but isn't that against the current Ruby standards?
> 
> I can see your point, but I'd still like to reduce this pain and I was hoping by adding the drivers to the cookbooks slowly could be a starting point.
> 
> —
> Reply to this email directly or view it on GitHub.