There are two things that need to happen for this to be resolved:
[ ] Actually write some meaningful specs ( #4 )
[ ] Update the .travis.yml install different versions of bundler ( #4 )
The first is obvious, though, I think what we want to be testing as part of this is actually running bundle install against a test Gemfile with override_gem being used, and confirm things are working as expected (subsequent after subsequent bundle updates and executing some code as well. So very integration style tests that probably make use of a spec/support/dummy/ directory to handle that.
Granted, this code is pretty battle tested, but it would be nice knowing that it works for bundler versions we aren't using regularly... which leads to the next point...
Testing multiple versions on travis should be pretty easy, and we probably could change the .travis.yml to do something like this:
There are two things that need to happen for this to be resolved:
.travis.ymlinstall different versions of bundler ( #4 )The first is obvious, though, I think what we want to be testing as part of this is actually running
bundle installagainst a testGemfilewithoverride_gembeing used, and confirm things are working as expected (subsequent after subsequentbundle updates and executing some code as well. So very integration style tests that probably make use of aspec/support/dummy/directory to handle that.Granted, this code is pretty battle tested, but it would be nice knowing that it works for
bundlerversions we aren't using regularly... which leads to the next point...Testing multiple versions on travis should be pretty easy, and we probably could change the
.travis.ymlto do something like this:Or something similar.