testbeds 0.0.1

data/.gitignore

@@ -0,0 +1,18 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+spec/testbeds

data/.travis.yml

@@ -0,0 +1,9 @@
+before_script:
+  # only if you don't commit the testbeds to git
+  - generate-testbeds
+
+script: "rake testbeds:current:rspec"
+
+gemfiles:
+  - path/to/gemfiles/rails-3.2
+  - path/to/gemfiles/rails-4.0

data/Bedfile

@@ -0,0 +1,15 @@
+store_in "spec/testbeds"
+
+testbeds do
+  gemfiles 'gemfiles/rails-3.2',
+           'gemfiles/rails-4.0'
+
+  init do
+    run "rails", "new", name, "--skip-bundle", "--skip-gemfile"
+    chdir name
+    run "rails", "g", "rspec:install"
+  end
+
+  rakefile '<%= name %>/Rakefile'
+  depend_on '<%= name %>/config/application.rb'
+end

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in testbeds.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Colin MacKenzie IV
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,237 @@
+# Testbeds
+
+It's not very easy to test your gem in many different environments. Take
+for example Rails: how can you know that your gem, tested in a Rails 3.2 app,
+will work in Rails 4.0, without regenerating the entire app? And after doing
+so, how will you ensure backward compatibility to 3.2 going forward?
+
+Those are the sorts of problems this gem is meant to help with.
+
+## 1. Pull in the gem (duh)
+
+First, add this gem to your project's list of development dependencies:
+
+    # in my-gem.gemspec
+    gem.add_development_dependency 'testbeds'
+
+Then install it, of course.
+
+## 2. Create Gemfiles (yes, more than one)
+
+Add a Gemfile for each testbed you intend to implement. For example, you
+might have a file in `gemfiles/rails-3.2` describing your dependencies for
+testing within Rails 3.2, and another in `gemfiles/rails-4.0` which could
+have a completely different set of dependencies.
+
+## 3. The Bedfile
+
+Then, create a `Bedfile` and use the handy-dandy DSL to build up your 
+testbeds. Here's an example `Bedfile`:
+
+    # store testbeds in spec/testbeds/*
+    store_in "spec/testbeds"
+
+    testbeds do
+      # create 2 testbeds, one for Rails 3.2 and the other for Rails 4.0
+      gemfiles 'gemfiles/rails-3.2',
+               'gemfiles/rails-4.0'
+
+      init do
+        # when generating each testbed, first generate a Rails app...
+        run "rails", "new", name, "--skip-bundle", "--skip-gemfile"
+        chdir name
+
+        # ...and then run the rspec-rails installer.
+        run "rails", "g", "rspec:install"
+      end
+
+      # Load this Rakefile. More on this later.
+      rakefile '<%= name %>/Rakefile'
+
+      # Load this file as a dependency whenever code is executed in
+      # the context of this testbed. More on this later.
+      depend_on '<%= name %>/config/application.rb'
+    end
+
+There are only a few methods to be aware of:
+
+  * `store_in` - sets the destination directory which will serve as the
+    root of all of your testbeds. This is where the projects will be
+    generated.
+
+  * `testbeds do ... end` - Sets up one or more testbeds. You can call this
+    method more than once, with different setup code for each invocation,
+    or you can just call this method once.
+
+  * `gemfiles` - Takes a list of paths to Gemfiles, relative to the
+    `Bedfile`. Each Gemfile represents a testbed. All of the other set-up
+    in this `testbeds do ... end` block will be duplicated once for each
+    Gemfile.
+
+  * `init do ... end` - Runs the given block when a testbed is being
+    generated. This allows you to take whatever steps would be normally
+    taken by a user of your gem within the target environment. In the 
+    above example, we generate a Rails application and then run the
+    rspec-rails installer, but this is only an example.
+
+  * `rakefile` - Takes a path relative to `store_in` for loading Rake tasks.
+    In your main `Rakefile`, you can just `require 'testbeds/rake'`. See
+    the `Rake` section, below.
+
+  * `depend_on` - Specifies the files within the testbed(s) which must be
+    loaded whenever the testbed is being used. See the `Rake` section, below.
+
+## 4. Generating Testbeds
+
+When you're ready to build your testbeds, run the `generate-testbeds` script
+that ships with this gem. It will remove everything in the `store_in` 
+directory (so watch out!) and then start generating testbeds from scratch.
+We purposely wipe out the previous state here, because we want to be able to
+build up each testbed from a clean slate. In fact, you could opt not to even
+commit the `store_in` directory to Git. (I haven't decided yet whether to
+consider adding `store_in` to `.gitignore` a best practice, so consider it
+a matter of opinion.)
+
+At each stage of testbed generation, the command that is about to be executed
+is printed to the screen for your reference. This way, if it fails, you will
+know exactly at what point the failure occurred.
+
+Here's an example of what testbed generation looks like:
+
+    colin in testbeds  $ generate-testbeds 
+
+    rm -rf /Users/colin/projects/gems/testbeds/spec/testbeds
+    mkdir -p /Users/colin/projects/gems/testbeds/spec/testbeds
+    export BUNDLE_GEMFILE="/Users/colin/projects/gems/testbeds/gemfiles/rails-3.2"
+    bundle install
+    bundle exec rails new rails-3.2 --skip-bundle --skip-gemfile
+    bundle exec rails g rspec:install
+
+    export BUNDLE_GEMFILE="/Users/colin/projects/gems/testbeds/gemfiles/rails-4.0"
+    bundle install
+    bundle exec rails new rails-4.0 --skip-bundle --skip-gemfile
+    bundle exec rails g rspec:install
+
+
+### Note about `BUNDLE_GEMFILE`
+
+As you can see, `BUNDLE_GEMFILE` is exported at each stage. This gem relies
+heavily on Bundler in this way. I think it's probably a bad idea to execute
+`bundle execute generate-testbeds`, as this will create an environment that
+conflicts with the testbed environments. I'm not sure what to expect in such
+a state. You have been warned -- but I'll still accept pull requests if it
+leads to fixable bugs.
+
+## 5. Rake
+
+Instead of trying to guess at a once-size-fits-all set of Rake tasks, I
+decided after some deliberation that this gem should instead focus on
+augmenting tasks written _by you_. So it's not a one-line drop-in sort of
+thing. Instead it provides you the tools you need to run a Rake task
+in one or more testbeds of your choosing.
+
+Here's a typical `Rakefile` that makes use of this gem:
+
+    # in Rakefile
+    require 'testbeds/rake'
+    require 'rspec/core/rake_task'
+
+    # each_testbed yields a testbed itself, and also creates the corresponding
+    # Rake namespace for the testbed.
+    each_testbed do |testbed| # namespace 'testbed:rails-3.2'
+
+      # create a namespaced rspec task for each testbed
+      desc "run rspec tests in #{testbed.name}"
+      task :rspec do
+        ENV['BUNDLE_GEMFILE'] = testbed.gemfile
+
+        # so here we'll create an RSpec task at runtime, and then invoke
+        # it right away. You don't have to do it this way, but I chose to,
+        # in order to silence some RSpec cruft at the command line.
+        RSpec::Core::RakeTask.new("_rspec") do |t|
+          opts = testbed.dependencies.collect { |dep| ['-r', dep] }.flatten
+          t.rspec_opts = opts
+        end
+
+        Rake::Task["_rspec"].invoke
+      end
+
+    end
+
+    desc 'run rspec tests in each testbed consecutively'
+    task :rspec do
+      each_testbed do |testbed|
+        raise unless system "rake #{testbed.namespace}:rspec"
+      end
+    end
+
+When you have a `Rakefile` like this, running `rake --tasks` will show
+about what you'd expect:
+
+    rake build                     # Build testbeds-0.0.1.gem into the pkg directory.
+    rake install                   # Build and install testbeds-0.0.1.gem into system gems.
+    rake release                   # Create tag v0.0.1 and build and push testbeds-0.0.1.gem to Rubygems
+    rake rspec                     # run rspec tests in each testbed consecutively
+    rake testbed:rails-3.2:rspec   # run rspec tests in rails-3.2
+    rake testbed:rails-4.0:rspec   # run rspec tests in rails-4.0
+
+As you can see, we've namespaced each `rspec` task into its own testbed
+namespace. This allows us to run the specs under, say, just the `rails-3.2`
+testbed, ignoring for the moment the same specs under `rails-4.0`. We also
+have the no-namespace `rake rspec` task, which will iterate through each
+testbed and execute its specs consecutively. If any one of these fails,
+the whole process will be aborted.
+
+### Testbed Rake Tasks
+
+There's one more thing you can do that is really cool, but not so obvious.
+If you export the environment variable `BUNDLE_GEMFILE` pointing to one of
+your testbed Gemfiles, then you get:
+
+    $ BUNDLE_GEMFILE=gemfiles/rails-3.2 rake -T
+
+    rake build                              # Build testbeds-0.0.1.gem into the pkg directory.
+    rake install                            # Build and install testbeds-0.0.1.gem into system gems.
+    rake release                            # Create tag v0.0.1 and build and push testbeds-0.0.1.gem to Rubygems
+    rake rspec                              # run rspec tests in each testbed consecutively
+    rake testbed:current:about              # List versions of all Rails frameworks and the environment
+    rake testbed:current:assets:clean       # Remove compiled assets
+    rake testbed:current:assets:precompile  # Compile all the assets named in config.assets.precompile
+    rake testbed:current:db:create          # Create the database from config/database.yml for the current Rails.env (use db:create:a...
+    rake testbed:current:db:drop            # Drops the database for the current Rails.env (use db:drop:all to drop all databases)
+    rake testbed:current:db:fixtures:load   # Load fixtures into the current environment's database.
+    rake testbed:current:db:migrate         # Migrate the database (options: VERSION=x, VERBOSE=false).
+      < snip, long list >
+    rake testbed:current:tmp:create         # Creates tmp directories for sessions, cache, sockets, and pids
+    rake testbed:rails-3.2:rspec            # run rspec tests in rails-3.2
+    rake testbed:rails-4.0:rspec            # run rspec tests in rails-4.0
+
+As you can see, this syntax creates another namespace, `testbed:current`,
+which contains the Rake tasks loaded for this testbed. This gives you a
+convenient handle for e.g. running migrations and the like without having
+to move from testbed to testbed.
+
+## 6. Travis
+
+You test on travis-ci.org, right? Yes, of course you do, and you want to run
+your tests on each testbed, every time you commit. Here's how:
+
+    # in .travis.yml
+    before_script:
+      # only if you don't commit the testbeds to git
+      - generate-testbeds
+
+    script: "rake testbeds:current:rspec"
+
+    gemfile:
+      - path/to/gemfiles/rails-3.2
+      - path/to/gemfiles/rails-4.0
+
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1,24 @@
+require "bundler/gem_tasks"
+
+# in Rakefile
+require 'testbeds/rake'
+require 'rspec/core/rake_task'
+
+each_testbed do |testbed| # namespace 'testbed:rails-3.2'
+  desc "run rspec tests in #{testbed.name}"
+  task :rspec do
+    ENV['BUNDLE_GEMFILE'] = testbed.gemfile
+    RSpec::Core::RakeTask.new("_rspec") do |t|
+      opts = testbed.dependencies.collect { |dep| ['-r', dep] }.flatten
+      t.rspec_opts = opts
+    end
+    Rake::Task["_rspec"].invoke
+  end
+end
+
+desc 'run rspec tests in each testbed consecutively'
+task :rspec do
+  each_testbed do |testbed|
+    raise unless system "rake #{testbed.namespace}:rspec"
+  end
+end

data/bin/generate-testbeds

@@ -0,0 +1,62 @@
+#!/usr/bin/env ruby
+
+require File.expand_path('../lib/testbeds', File.dirname(__FILE__))
+require 'fileutils'
+
+include FileUtils
+
+def run *command
+  puts "bundle exec #{command.join(' ')}"
+  if ENV["VERBOSE"]
+    if command.length == 1
+      result = system "bundle exec #{command}"
+    else
+      result = system "bundle", "exec", *command.collect { |c| c.to_s }
+    end
+    raise "Command failed" unless result
+  else
+    output = `bundle exec #{command.join(' ')}`
+    raise "Command failed\n\n#{output}" unless $?.success?
+  end
+end
+
+if testbed = Testbeds.current
+  testbed_directory = testbed.store_in.to_s
+
+  chdir testbed_directory
+
+  puts 'bundle install'
+  if ENV['VERBOSE']
+    unless system 'bundle install'
+      raise "Couldn't install bundle for testbed #{testbed.name}"
+    end
+  else
+    output = `bundle install`
+    unless $?.success?
+      raise "Couldn't install bundle for testbed #{testbed.name}\n\n#{output}"
+    end
+  end
+
+  testbed.run_init_script
+else
+  cleared = {}
+  Testbeds.each do |testbed|
+    testbed_directory = testbed.store_in.to_s
+
+    unless cleared[testbed_directory]
+      if File.directory?(testbed_directory)
+        puts "rm -rf #{testbed_directory}"
+        rm_rf testbed_directory
+        cleared[testbed_directory] = 1
+      end
+
+      puts "mkdir -p #{testbed_directory}"
+      mkdir_p testbed_directory 
+    end
+
+    puts "export BUNDLE_GEMFILE=#{testbed.gemfile.to_s.inspect}"
+    ENV['BUNDLE_GEMFILE'] = testbed.gemfile
+    raise "Testbed #{testbed.name} generation failed" unless system $0
+    puts
+  end
+end

data/gemfiles/rails-3.2

@@ -0,0 +1,4 @@
+source "http://rubygems.org"
+
+gem 'rails', '~> 3.2'
+gem 'rspec-rails'

data/gemfiles/rails-3.2.lock

@@ -0,0 +1,98 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    actionmailer (3.2.0)
+      actionpack (= 3.2.0)
+      mail (~> 2.4.0)
+    actionpack (3.2.0)
+      activemodel (= 3.2.0)
+      activesupport (= 3.2.0)
+      builder (~> 3.0.0)
+      erubis (~> 2.7.0)
+      journey (~> 1.0.0)
+      rack (~> 1.4.0)
+      rack-cache (~> 1.1)
+      rack-test (~> 0.6.1)
+      sprockets (~> 2.1.2)
+    activemodel (3.2.0)
+      activesupport (= 3.2.0)
+      builder (~> 3.0.0)
+    activerecord (3.2.0)
+      activemodel (= 3.2.0)
+      activesupport (= 3.2.0)
+      arel (~> 3.0.0)
+      tzinfo (~> 0.3.29)
+    activeresource (3.2.0)
+      activemodel (= 3.2.0)
+      activesupport (= 3.2.0)
+    activesupport (3.2.0)
+      i18n (~> 0.6)
+      multi_json (~> 1.0)
+    arel (3.0.2)
+    builder (3.0.4)
+    diff-lcs (1.2.4)
+    erubis (2.7.0)
+    hike (1.2.1)
+    i18n (0.6.1)
+    journey (1.0.4)
+    json (1.7.5)
+    mail (2.4.4)
+      i18n (>= 0.4.0)
+      mime-types (~> 1.16)
+      treetop (~> 1.4.8)
+    mime-types (1.22)
+    multi_json (1.7.2)
+    polyglot (0.3.3)
+    rack (1.4.1)
+    rack-cache (1.2)
+      rack (>= 0.4)
+    rack-ssl (1.3.2)
+      rack
+    rack-test (0.6.2)
+      rack (>= 1.0)
+    rails (3.2.0)
+      actionmailer (= 3.2.0)
+      actionpack (= 3.2.0)
+      activerecord (= 3.2.0)
+      activeresource (= 3.2.0)
+      activesupport (= 3.2.0)
+      bundler (~> 1.0)
+      railties (= 3.2.0)
+    railties (3.2.0)
+      actionpack (= 3.2.0)
+      activesupport (= 3.2.0)
+      rack-ssl (~> 1.3.2)
+      rake (>= 0.8.7)
+      rdoc (~> 3.4)
+      thor (~> 0.14.6)
+    rake (10.0.4)
+    rdoc (3.12)
+      json (~> 1.4)
+    rspec-core (2.13.1)
+    rspec-expectations (2.13.0)
+      diff-lcs (>= 1.1.3, < 2.0)
+    rspec-mocks (2.13.1)
+    rspec-rails (2.13.1)
+      actionpack (>= 3.0)
+      activesupport (>= 3.0)
+      railties (>= 3.0)
+      rspec-core (~> 2.13.0)
+      rspec-expectations (~> 2.13.0)
+      rspec-mocks (~> 2.13.0)
+    sprockets (2.1.3)
+      hike (~> 1.2)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
+    thor (0.14.6)
+    tilt (1.3.6)
+    treetop (1.4.12)
+      polyglot
+      polyglot (>= 0.3.1)
+    tzinfo (0.3.37)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  rails (~> 3.2)
+  rspec-rails

data/gemfiles/rails-4.0

@@ -0,0 +1,7 @@
+source "http://rubygems.org"
+
+gem 'rails', '~> 4.0.0.beta1'
+gem 'coffee-rails', '~> 4.0.0.beta1'
+gem 'sass-rails', '~> 4.0.0.beta1'
+gem 'turbolinks'
+gem 'rspec-rails'

data/gemfiles/rails-4.0.lock

@@ -0,0 +1,114 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    actionmailer (4.0.0.rc1)
+      actionpack (= 4.0.0.rc1)
+      mail (~> 2.5.3)
+    actionpack (4.0.0.rc1)
+      activesupport (= 4.0.0.rc1)
+      builder (~> 3.1.0)
+      erubis (~> 2.7.0)
+      rack (~> 1.5.2)
+      rack-test (~> 0.6.2)
+    activemodel (4.0.0.rc1)
+      activesupport (= 4.0.0.rc1)
+      builder (~> 3.1.0)
+    activerecord (4.0.0.rc1)
+      activemodel (= 4.0.0.rc1)
+      activerecord-deprecated_finders (~> 1.0.2)
+      activesupport (= 4.0.0.rc1)
+      arel (~> 4.0.0)
+    activerecord-deprecated_finders (1.0.2)
+    activesupport (4.0.0.rc1)
+      i18n (~> 0.6, >= 0.6.4)
+      minitest (~> 4.2)
+      multi_json (~> 1.3)
+      thread_safe (~> 0.1)
+      tzinfo (~> 0.3.37)
+    arel (4.0.0)
+    atomic (1.1.8)
+    builder (3.1.4)
+    coffee-rails (4.0.0)
+      coffee-script (>= 2.2.0)
+      railties (>= 4.0.0.beta, < 5.0)
+    coffee-script (2.2.0)
+      coffee-script-source
+      execjs
+    coffee-script-source (1.6.2)
+    diff-lcs (1.2.4)
+    erubis (2.7.0)
+    execjs (1.4.0)
+      multi_json (~> 1.0)
+    hike (1.2.2)
+    i18n (0.6.4)
+    mail (2.5.3)
+      i18n (>= 0.4.0)
+      mime-types (~> 1.16)
+      treetop (~> 1.4.8)
+    mime-types (1.23)
+    minitest (4.7.4)
+    multi_json (1.7.2)
+    polyglot (0.3.3)
+    rack (1.5.2)
+    rack-test (0.6.2)
+      rack (>= 1.0)
+    rails (4.0.0.rc1)
+      actionmailer (= 4.0.0.rc1)
+      actionpack (= 4.0.0.rc1)
+      activerecord (= 4.0.0.rc1)
+      activesupport (= 4.0.0.rc1)
+      bundler (>= 1.3.0, < 2.0)
+      railties (= 4.0.0.rc1)
+      sprockets-rails (~> 2.0.0.rc4)
+    railties (4.0.0.rc1)
+      actionpack (= 4.0.0.rc1)
+      activesupport (= 4.0.0.rc1)
+      rake (>= 0.8.7)
+      thor (>= 0.18.1, < 2.0)
+    rake (10.0.4)
+    rspec-core (2.13.1)
+    rspec-expectations (2.13.0)
+      diff-lcs (>= 1.1.3, < 2.0)
+    rspec-mocks (2.13.1)
+    rspec-rails (2.13.1)
+      actionpack (>= 3.0)
+      activesupport (>= 3.0)
+      railties (>= 3.0)
+      rspec-core (~> 2.13.0)
+      rspec-expectations (~> 2.13.0)
+      rspec-mocks (~> 2.13.0)
+    sass (3.2.8)
+    sass-rails (4.0.0.rc1)
+      railties (>= 4.0.0.beta, < 5.0)
+      sass (>= 3.1.10)
+      sprockets-rails (~> 2.0.0.rc0)
+      tilt (~> 1.3)
+    sprockets (2.9.3)
+      hike (~> 1.2)
+      multi_json (~> 1.0)
+      rack (~> 1.0)
+      tilt (~> 1.1, != 1.3.0)
+    sprockets-rails (2.0.0.rc4)
+      actionpack (>= 3.0)
+      activesupport (>= 3.0)
+      sprockets (~> 2.8)
+    thor (0.18.1)
+    thread_safe (0.1.0)
+      atomic
+    tilt (1.4.0)
+    treetop (1.4.12)
+      polyglot
+      polyglot (>= 0.3.1)
+    turbolinks (1.1.1)
+      coffee-rails
+    tzinfo (0.3.37)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  coffee-rails (~> 4.0.0.beta1)
+  rails (~> 4.0.0.beta1)
+  rspec-rails
+  sass-rails (~> 4.0.0.beta1)
+  turbolinks

data/lib/testbeds/bed.rb

@@ -0,0 +1,33 @@
+require 'erb'
+
+module Testbeds
+  class Bed
+    attr_reader :gemfile, :dependencies, :rakefile, :store_in
+
+    def namespace
+      "testbed:#{name}"
+    end
+
+    def template str
+      ERB.new(str).result(binding)
+    end
+
+    def name
+      @name ||= Pathname.new File.basename(gemfile)
+    end
+
+    def run_init_script
+      instance_eval &@init_script if @init_script
+    end
+
+    def initialize gemfile, dependencies, rakefile, init_script, store_in
+      @store_in     = Pathname.new File.expand_path(store_in)
+      @gemfile      = File.expand_path gemfile
+      @rakefile     = @store_in.join template(rakefile)
+      @init_script  = init_script
+      @dependencies = dependencies.collect do |dep|
+        @store_in.join template(dep)
+      end
+    end
+  end
+end

data/lib/testbeds/index/testbed.rb

@@ -0,0 +1,36 @@
+module Testbeds
+  class Index
+    class Testbed
+      def initialize store_in, &block
+        @gemfiles = []
+        @dependencies = []
+        @rakefile = "Rakefile"
+        @init_script = nil
+        @store_in = store_in
+        instance_eval &block
+      end
+
+      def gemfiles *gemfiles
+        @gemfiles.concat gemfiles.flatten
+      end
+
+      def init &block
+        @init_script = block
+      end
+
+      def rakefile template
+        @rakefile = template
+      end
+
+      def depend_on *deps
+        @dependencies.concat deps.flatten
+      end
+
+      def flatten
+        gemfiles.collect do |gemfile|
+          Testbeds::Bed.new gemfile, @dependencies, @rakefile, @init_script, @store_in
+        end
+      end
+    end
+  end
+end

data/lib/testbeds/index.rb

@@ -0,0 +1,31 @@
+module Testbeds
+  class Index
+    attr_reader :beds
+
+    def find_index_file base_path = Pathname.new('.')
+      path = File.expand_path(base_path.join('Bedfile'))
+      return path if File.file?(path)
+      # if we hit root, there is no Bedfile
+      return nil if path =~ /:\\Bedfile/ or path =~ /^\/Bedfile/
+      find_index_file base_path.join('..')
+    end
+
+    def initialize
+      @store_in = "testbeds"
+      @beds = []
+      raise "no Bedfile found" unless file = find_index_file
+      src = File.read file
+      eval src, binding, file
+    end
+
+    def testbeds &block
+      @beds.concat Testbeds::Index::Testbed.new(@store_in, &block).flatten
+    end
+
+    alias_method :testbed, :testbeds
+
+    def store_in dest
+      @store_in = dest
+    end
+  end
+end

data/lib/testbeds/rake/dsl.rb

@@ -0,0 +1,19 @@
+module Testbeds
+  module Rake
+    module DSL
+      def each_testbed
+        if current = Testbeds.current
+          namespace 'testbed:current' do
+            yield current
+          end
+        end
+
+        Testbeds.each do |testbed|
+          namespace testbed.namespace do
+            yield testbed
+          end
+        end
+      end
+    end
+  end
+end

data/lib/testbeds/rake.rb

@@ -0,0 +1,8 @@
+require 'testbeds'
+require "testbeds/rake/dsl"
+extend Testbeds::Rake::DSL
+if testbed = Testbeds.current
+  namespace "testbed:current" do
+    load testbed.rakefile if File.file?(testbed.rakefile)
+  end
+end

data/lib/testbeds/version.rb

@@ -0,0 +1,3 @@
+module Testbeds
+  VERSION = "0.0.1"
+end

data/lib/testbeds.rb

@@ -0,0 +1,32 @@
+$:.unshift File.dirname(__FILE__)
+
+require 'pathname'
+
+require "testbeds/version"
+require "testbeds/index"
+require "testbeds/bed"
+require "testbeds/index/testbed"
+
+module Testbeds
+  module_function
+
+  def all
+    @testbeds ||= Testbeds::Index.new.beds
+  end
+
+  def each &block
+    all.each &block
+  end
+
+  def current
+    if current_gemfile = ENV['BUNDLE_GEMFILE']
+      all.each do |testbed|
+        if testbed.gemfile == File.expand_path(current_gemfile)
+          return testbed
+        end
+      end
+    end
+
+    nil
+  end
+end

data/spec/test_spec.rb

@@ -0,0 +1,19 @@
+# Dummy file to trick RSpec into actually running (and reporting 0 specs).
+#
+# I'm not clear on the best way to test this gem. For now, here is my
+# process (and beware, it's not automated!):
+#
+#   1. Regenerate testbeds with `bin/generate-testbeds`.
+#
+#   2. Examine directory structure, particularly that `spec/testbeds`
+#      is created and that it contains one subdirectory for each gemfile.
+#
+#   3. Run `rake -T` and ensure that RSpec tests appear for each testbed.
+#
+#   4. Run `rake rspec` and ensure that RSpec runs twice. Examine the output
+#      to ensure that each execution of RSpec includes a different
+#      bootstrap to config/application.rb -- one for each testbed.
+#
+# I know that testing this way is a horrible, horrible idea, but I've come up
+# short in thinking of better ways to do this. I'm accepting pull requests.
+#

data/testbeds.gemspec

@@ -0,0 +1,19 @@
+# -*- encoding: utf-8 -*-
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'testbeds/version'
+
+Gem::Specification.new do |gem|
+  gem.name          = "testbeds"
+  gem.version       = Testbeds::VERSION
+  gem.authors       = ["Colin MacKenzie IV"]
+  gem.email         = ["sinisterchipmunk@gmail.com"]
+  gem.description   = "Manage multiple testbed environments for your gems"
+  gem.summary       = "Manage multiple testbed environments for your gems"
+  gem.homepage      = "http://github.com/sinisterchipmunk/testbeds"
+
+  gem.files         = `git ls-files`.split($/)
+  gem.executables   = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
+  gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
+  gem.require_paths = ["lib"]
+end

metadata

@@ -0,0 +1,68 @@
+--- !ruby/object:Gem::Specification
+name: testbeds
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+  prerelease: 
+platform: ruby
+authors:
+- Colin MacKenzie IV
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2013-05-12 00:00:00.000000000 Z
+dependencies: []
+description: Manage multiple testbed environments for your gems
+email:
+- sinisterchipmunk@gmail.com
+executables:
+- generate-testbeds
+extensions: []
+extra_rdoc_files: []
+files:
+- .gitignore
+- .travis.yml
+- Bedfile
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/generate-testbeds
+- gemfiles/rails-3.2
+- gemfiles/rails-3.2.lock
+- gemfiles/rails-4.0
+- gemfiles/rails-4.0.lock
+- lib/testbeds.rb
+- lib/testbeds/bed.rb
+- lib/testbeds/index.rb
+- lib/testbeds/index/testbed.rb
+- lib/testbeds/rake.rb
+- lib/testbeds/rake/dsl.rb
+- lib/testbeds/version.rb
+- spec/test_spec.rb
+- testbeds.gemspec
+homepage: http://github.com/sinisterchipmunk/testbeds
+licenses: []
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 1.8.24
+signing_key: 
+specification_version: 3
+summary: Manage multiple testbed environments for your gems
+test_files:
+- spec/test_spec.rb