busser-rspec 0.8.0 → 0.8.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 82e172f3398ede4750b0d602530d06e37db0c38a2fec89e8858ae10d0850f68d
-  data.tar.gz: a670fbd169b448cc53f4f2f11ba722bb6ce3781db0443bc32b8ae1d074fe7cc4
+  metadata.gz: 217c8f2f4bb8a712f4d69e22c3567334306c9d0e44cdc418c47630ee84660ffe
+  data.tar.gz: cf85c2e7e49b49c74273c9d2f11ee208d3eadead985ff3f9f021a7e35ace6b53
 SHA512:
-  metadata.gz: 4d628d8fe580fc8323ff9d33bc783009ec3498fcbeba567280b48c1319f1ddf55c0971e13cdbf7eb0dfbc9ae718218a50f7b8b6a6cbe19fa4df7751b15ee99c6
-  data.tar.gz: d1f5c0f5f40f9015ca3d225df90535835f98347425325be9c3d102dcfca4445a5f067149399c871a4ba90ed12f0997c6ea2a4a3db7457170df058afd011d0aa3
+  metadata.gz: 677c89b4864b780207555fcfe5b176e172e50c2a77ecdfd8ce8f5723fb0988250c3e9e03bacf3781f3a5486eed4050e8a5a1415288f4f1396eb4bcc239d5bc1c
+  data.tar.gz: a1ed580c340581807850947ee6ce8f391483dd809aa98efb86c7960af31318e468244c63f671948e85540fe98fcf70190dfb966fe5080e3d4d453d3153db64d0

data/.github/workflows/publish.yml

@@ -43,3 +43,25 @@ jobs:
         uses: actionshub/publish-gem-to-rubygems@f9126f7a2d36a4fd31a13e78fde5fbdcc4b7b251  # v2.0.6
         with:
           token: ${{ secrets.RUBYGEMS_API_KEY }}
+
+      # actionshub/publish-gem-to-rubygems logs a rejected push and still exits
+      # 0, so a release that never reached RubyGems shows up as a green job.
+      # Ask RubyGems directly instead of trusting the step. The v2 endpoint is
+      # 404 until the exact version is indexed, so -f turns "not there" into a
+      # non-zero exit rather than a substring match on `gem list` output.
+      - name: Verify the release reached RubyGems
+        if: ${{ steps.release.outputs.release_created }}
+        env:
+          VERSION: ${{ steps.release.outputs.version }}
+        run: |
+          set -euo pipefail
+          name="$(basename "$(ls ./*.gemspec)" .gemspec)"
+          for _ in $(seq 1 12); do
+            if curl -fsS -o /dev/null "https://rubygems.org/api/v2/rubygems/${name}/versions/${VERSION}.json"; then
+              echo "${name} ${VERSION} is on RubyGems"
+              exit 0
+            fi
+            sleep 15
+          done
+          echo "::error::${name} ${VERSION} never reached RubyGems. A permissions failure in the push step above does not fail that step -- read its log."
+          exit 1

data/.gitignore

@@ -6,7 +6,6 @@
 Gemfile.lock
 InstalledFiles
 _yardoc
-coverage
 doc/
 lib/bundler/man
 pkg

data/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.8.0"
+  ".": "0.8.1"
 }

data/.rubocop.yml

@@ -3,7 +3,4 @@ require:
   - cookstyle/chefstyle
 
 AllCops:
-  TargetRubyVersion: 3.1
-  Exclude:
-    - "vendor/**/*"
-    - "spec/**/*"
+  TargetRubyVersion: 3.2

data/CHANGELOG.md

@@ -3,6 +3,13 @@
 * Additional windows fixes for recent Omnibus Chef
 * Documentation (`README`) updates
 
+## [0.8.1](https://github.com/test-kitchen/busser-rspec/compare/v0.8.0...v0.8.1) (2026-08-28)
+
+
+### Bug Fixes
+
+* quote paths before handing them to a shell ([#30](https://github.com/test-kitchen/busser-rspec/issues/30)) ([9410c75](https://github.com/test-kitchen/busser-rspec/commit/9410c755924525ab436e27beb017b7f43a8453bc))
+
 ## [0.8.0](https://github.com/test-kitchen/busser-rspec/compare/v0.7.6...v0.8.0) (2026-08-28)
 
 

data/CONTRIBUTING.md

@@ -0,0 +1,104 @@
+# Contributing to busser-rspec
+
+Thanks for taking the time to contribute. This document covers how to get the
+project running locally, how to check your work before opening a pull request,
+and the commit convention releases depend on.
+
+## Getting set up
+
+This plugin requires **Ruby 3.2 or newer**. Clone the repository and install the
+development dependencies:
+
+```bash
+git clone https://github.com/test-kitchen/busser-rspec.git
+cd busser-rspec
+bundle install
+```
+
+## Running the tests
+
+`rake` runs the whole suite:
+
+```bash
+bundle exec rake test
+```
+
+The tests are [cucumber](https://cucumber.io) features in `features/`. They
+drive the real `busser` executable through
+[aruba](https://github.com/cucumber/aruba) rather than calling the plugin's
+classes, so they cover it end to end: install the plugin into a throwaway
+Busser root, write a suite, run it, and check what came out. The step
+definitions they use are published by busser itself, in `lib/busser/cucumber.rb`.
+
+### How the feature sandbox works
+
+Features that install the plugin sandbox `GEM_HOME` into a temporary directory
+and strip bundler out of the environment, so a run never installs a gem into
+your bundle. Two details matter if you add or change one:
+
+* **Do not reintroduce bundler variables.** RubyGems re-requires
+  `bundler/setup` whenever `BUNDLER_SETUP` is present, and bundler then resets
+  `Gem.dir` to the bundle. Plugins install into `vendor/bundle` instead of the
+  sandbox, and the assertions that look in `GEM_HOME` fail. The
+  `a non bundler environment` step exists to clear this.
+* **The plugin is installed from the working tree.** With bundler out of the
+  way, `busser plugin install` would fetch the last release from RubyGems and
+  run *its* postinstall — so the suite would pass on code that is not in your
+  branch. The `this plugin is installed from the working tree` step builds the
+  gem from the gemspec and installs it into the sandbox first, which is what
+  makes the features test your change.
+
+## Linting
+
+CI runs three linters, all of which you can run locally:
+
+```bash
+bundle exec cookstyle --chefstyle   # Ruby
+yamllint --strict .                 # YAML
+markdownlint-cli2 "**/*.md" "!**/CHANGELOG*.md"
+```
+
+## Commit messages
+
+This project uses [Conventional Commits](https://www.conventionalcommits.org).
+Releases are automated, and the commit subject on `main` is what decides the
+next version number and what appears in the changelog.
+
+Pull requests are **squash merged, so the pull request title becomes that
+subject**. A CI check enforces the format on the title; the individual commits
+on your branch are not checked.
+
+| Prefix | Effect on the next release |
+| --- | --- |
+| `fix:` | Patch version bump |
+| `feat:` | Minor version bump |
+| `feat!:`, or a `BREAKING CHANGE:` footer | Minor bump, until this gem reaches 1.0 |
+| `chore:`, `docs:`, `ci:`, `test:`, `refactor:` | No release |
+
+For example:
+
+```text
+fix: install the plugin into GEM_HOME rather than the bundle
+feat: support a Gemfile alongside the suite
+ci: pin the shared workflow to a release
+```
+
+## Opening a pull request
+
+1. Fork the repository and create a branch for your change.
+2. Add or update tests. A bug fix should come with a test that fails without it.
+3. Run `bundle exec rake test` and the linters above.
+4. Open a pull request with a Conventional Commits title.
+
+## Releases
+
+Releases are handled by
+[release-please](https://github.com/googleapis/release-please). It watches
+commits landing on `main` and keeps a release pull request open with the next
+version number and the accumulated changelog. Merging that pull request tags the
+release and publishes the gem to RubyGems and GitHub Packages.
+
+Maintainers do not bump `lib/busser/rspec/version.rb` or edit
+`CHANGELOG.md` by hand; release-please owns both files. This gem is still pre-1.0, so
+`bump-minor-pre-major` is set and a breaking change takes the minor rather than
+graduating it to 1.0.

data/Gemfile

@@ -3,13 +3,19 @@ source "https://rubygems.org"
 gemspec
 
 group :cookstyle do
-  gem "cookstyle", ">= 9.0.0"
+  gem "cookstyle", ">= 9.0"
 end
 
 group :test do
-  gem "aruba", ">= 2.0"
-  gem "base64" # cucumber needs it; not a default gem on Ruby 4.0
+  gem "aruba", ">= 2.4"
+  gem "base64", ">= 0.3" # cucumber needs it; not a default gem on Ruby 4.0
   gem "cucumber", ">= 11.1"
-  gem "rake"
+  gem "minitest", ">= 6.0"
+  gem "mocha", ">= 2.7"
+  gem "rake", ">= 13.4"
   gem "rspec", ">= 3.13"
 end
+
+group :development do
+  gem "yard", ">= 0.9.37"
+end

data/README.md

@@ -1,67 +1,149 @@
-# Busser::RunnerPlugin::Rspec
+# busser-rspec
 
 [![Gem Version](https://badge.fury.io/rb/busser-rspec.svg)](https://badge.fury.io/rb/busser-rspec)
 
-A Busser runner plugin for Rspec
+A [Busser](https://github.com/test-kitchen/busser) runner plugin that runs
+[RSpec](https://rspec.info) examples as integration tests.
+
+Busser installs RSpec on the machine under test during postinstall, then runs
+the suite's `rspec` directory against it. Because the examples run on the
+machine itself rather than over SSH, they can assert on local files, services
+and commands directly.
 
 ## Status
 
-This software project is no longer under active development as it has no active maintainers. The software may continue to work for some or all use cases, but issues filed in GitHub will most likely not be triaged. If a new maintainer is interested in working on this project please come chat with us in #test-kitchen on Chef Community Slack.
+This software project is no longer under active development as it has no active
+maintainers. The software may continue to work for some or all use cases, but
+issues filed in GitHub will most likely not be triaged. If a new maintainer is
+interested in working on this project please come chat with us in #test-kitchen
+on Chef Community Slack.
+
+## Requirements
 
-## Installation and Setup
+Ruby 3.2 or newer, and busser 0.9.0 or newer. The plugin installs RSpec 3.13 or
+newer on the machine under test.
 
-Please read the Busser [plugin usage](plugin_usage) page for more details.
+## Installation
+
+Busser installs the plugin for you when Test Kitchen runs the suite, so there is
+usually nothing to do. To install it by hand:
+
+```bash
+busser plugin install busser-rspec
+```
 
 ## Usage
 
-Please put test files into [COOKBOOK]/test/integration/[SUITES]/rspec/
+Put your specs in the `rspec` directory of a suite:
 
 ```text
--- [COOKBOOK]
-  `-- test
-     `-- integration
-        `-- default
-           `-- rspec
-              `-- spec_helper.rb
-              `-- Gemfile
+test
+`-- integration
+    `-- default              # suite name
+        `-- rspec
+            |-- Gemfile              # optional
+            |-- setup-recipe.rb      # optional
+            |-- spec_helper.rb
+            `-- default_spec.rb
+```
+
+The suite directory is passed to RSpec as the spec path, and both it and its
+`lib` subdirectory are added to the load path — so `require "spec_helper"` works
+from any spec without a relative path.
+
+```ruby
+describe "foobar::default" do
+  it "creates foobar.txt" do
+    expect(File).to exist("/usr/local/foobar.txt")
+  end
+end
+```
+
+### Extra gems
+
+If a `Gemfile` is present in the suite directory, it is `bundle install`ed
+before the run. Remember to include RSpec itself:
+
+```ruby
+source "https://rubygems.org"
+
+gem "rspec"
 ```
 
-You can specify your own test gem dependencies with a `Gemfile` under the `rspec` path, like this: `test/integration/<suite>/rspec/Gemfile`. Don't forget to put `gem "rspec"` there!
+The install is attempted with `--local` first and falls back to the network, so
+gems already present on the machine do not cost a download.
+
+### Chef setup
 
-## How do I ... ?
+If a `setup-recipe.rb` is present in the suite directory, it is applied with
+`chef-apply` before the specs run. This requires `/opt/chef/bin/chef-apply` on
+the machine; the run fails with a clear error if the file is there and Chef is
+not.
 
-### Change the rspec formatter?
+### Changing the formatter
 
-You may be familiar with using the `rspec -f` flag to change the rspec formatter. RSpec also offers a way to set the formatter from your specs:
+`rspec -f` is not available here, since Busser invokes the runner itself. Set
+the formatter from your specs instead:
 
 ```ruby
 RSpec.configure do |config|
-  # The same as `rspec -f documentation`
+  # the same as `rspec -f documentation`
   config.add_formatter "documentation"
+end
+```
+
+## Using it with Test Kitchen
+
+This is how most people run it, and it needs no Busser commands of your own.
+Select the verifier in `kitchen.yml`:
+
+```yaml
+verifier:
+  name: busser
+
+suites:
+  - name: default
 ```
 
-## Development
+Then put your tests in a `rspec` directory inside the suite:
 
-* Source hosted at [GitHub](https://github.com/opscode/busser-rspec)
-* Report issues/questions/feature requests on [GitHub Issues](issues)
+```text
+test/integration/default/rspec/default_spec.rb
+```
+
+`kitchen verify` installs Busser and this plugin on the instance and runs them.
+The directory name is what selects this plugin -- there is nothing else to
+configure.
+
+## When nothing runs
 
-Pull requests are very welcome! Make sure your patches are well tested.
-Ideally create a topic branch for every separate change you make. For
-example:
+If the suite files do not match what this plugin looks for, the run prints one
+line and **exits `0`**:
+
+```text
+-----> Running rspec test suite
+```
 
-1. Fork the repo
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Added some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
+No tests ran, and nothing said so. Work through these in order:
 
-## Authors
+1. **Is the directory named `rspec`?** That name alone selects this plugin.
+   `rspecs/`, `tests/` or anything else is not picked up.
+2. **Do the filenames match?** RSpec takes `*_spec.rb` -- `smoke.rb` is
+   *not* picked up.
+3. **Is the plugin installed?** `busser plugin list` shows what is available.
+4. **Is `BUSSER_ROOT` what you think?** `busser suite path` prints where suites
+   are actually being looked for.
 
-Created and maintained by Adam Jacob (<adam@opscode.com>)
+## Contributing
 
-Based on [busser-serverspec](https://github.com/cl-lab-k/busser-serverspec), created and maintained by HIGUCHI Daisuke (<d-higuchi@creationline.com>)
+Bug reports and pull requests are welcome. See
+[CONTRIBUTING.md](CONTRIBUTING.md) for how to set up the project, run the test
+suite, and format your commits.
 
 ## License
 
-Apache 2.0 (see [LICENSE](license))
+Apache License 2.0. See [LICENSE](LICENSE).
 
+Originally created by [Adam Jacob](https://github.com/adamhjk), based on
+[Daisuke Higuchi](https://github.com/cl-lab-k)'s
+[busser-serverspec](https://github.com/test-kitchen/busser-serverspec).

data/Rakefile

@@ -1,11 +1,36 @@
 require "bundler/gem_tasks"
+require "rake/testtask"
+Rake::TestTask.new(:unit) do |t|
+  t.libs.push "lib"
+  t.test_files = FileList["spec/**/*_spec.rb"]
+  t.verbose = true
+end
+
 require "cucumber/rake/task"
 
 Cucumber::Rake::Task.new(:features) do |t|
-  t.cucumber_opts = ["features", "-x", "--format progress"]
+  t.cucumber_opts = ["features", "--format progress", "--fail-fast"]
+end
+
+# yard lives in the :development group, which CI omits when it runs the tests.
+# Requiring it unconditionally would make `rake test` fail there, so the real
+# task is only defined when yard is installed and a stub explains its absence
+# otherwise. Nothing in CI gates on documentation.
+begin
+  require "yard"
+
+  YARD::Rake::YardocTask.new(:doc) do |t|
+    t.files = ["lib/**/*.rb"]
+    t.options = ["--output-dir", "doc", "--markup", "markdown"]
+  end
+rescue LoadError
+  desc "Generate YARD documentation (install the development group first)"
+  task :doc do
+    abort "yard is not available. Run `bundle install --with development` first."
+  end
 end
 
 desc "Run all test suites"
-task test: [:features]
+task test: %i{unit features}
 
 task default: [:test]

data/features/support/env.rb

@@ -11,13 +11,6 @@ Aruba.configure do |config|
   config.exit_timeout = 120
 end
 
-After do |s|
-  # Tell Cucumber to quit after this scenario is done - if it failed.
-  # This is useful to inspect the 'tmp/aruba' directory before any other
-  # steps are executed and clear it out.
-  Cucumber.wants_to_quit = true if s.failed?
-end
-
 # The sandboxed features shell out to `busser plugin install <this plugin>`, and
 # two things have to hold for that to exercise this checkout:
 #

data/lib/busser/rspec/version.rb

@@ -17,9 +17,10 @@
 
 module Busser
 
+  # Namespace for the RSpec Busser runner plugin.
   module Rspec
 
     # Version string for the Rspec Busser runner plugin
-    VERSION = "0.8.0".freeze
+    VERSION = "0.8.1".freeze
   end
 end

data/lib/busser/runner_plugin/rspec.rb

@@ -17,17 +17,85 @@
 
 require "busser/runner_plugin"
 require "rubygems" unless defined?(Gem)
+require "rbconfig" unless defined?(RbConfig)
+require "shellwords" unless defined?(Shellwords)
 
 # A Busser runner plugin for Rspec.
 #
 # @author Adam Jacob <adam@opscode.com>
 #
 class Busser::RunnerPlugin::Rspec < Busser::RunnerPlugin::Base
+
+  # Builds the command that runs the suite.
+  #
+  # The suite directory goes on the load path twice -- itself and its lib
+  # subdirectory -- so `require "spec_helper"` works from any spec without a
+  # relative path.
+  #
+  # Every path is quoted. BUSSER_ROOT is user supplied, and an unquoted path
+  # containing a space would be split by the shell into arguments RSpec would
+  # then treat as extra spec paths.
+  #
+  # @param runner [String] path to the runner script
+  # @param suite [String, Pathname] the suite directory holding the specs
+  # @return [String] the command to run
+  def self.runner_command(runner, suite)
+    suite = suite.to_s
+    [
+      Shellwords.escape(runner),
+      "-I", Shellwords.escape(suite),
+      "-I", Shellwords.escape(File.join(suite, "lib")),
+      Shellwords.escape(suite)
+    ].join(" ")
+  end
+
+  # Installs RSpec and bundler onto the machine under test. Runs once, when
+  # Busser installs this plugin.
+  # Builds the chef-apply command for a suite's setup recipe.
+  #
+  # @param setup_file [String, Pathname] path to the setup recipe
+  # @return [String] the command to run
+  def self.chef_apply_command(setup_file)
+    "/opt/chef/bin/chef-apply #{Shellwords.escape(setup_file.to_s)}"
+  end
+
+  # Builds the bundle install command for a suite's own Gemfile.
+  #
+  # bundler is invoked through the Ruby running Busser rather than whatever
+  # `bundle` is on PATH, since on a machine with several Rubies those differ and
+  # the suite's gems would land where the runner cannot see them.
+  #
+  # The --local attempt is a speed optimisation: it finishes immediately when
+  # the gems are already present and fails when it would need the network, so
+  # the second attempt is the fallback.
+  #
+  # @param gemfile [String, Pathname] path to the suite's Gemfile
+  # @return [String] the command to run
+  def self.bundle_install_command(gemfile)
+    bundle = [
+      Shellwords.escape(File.join(RbConfig::CONFIG["bindir"], "ruby")),
+      Shellwords.escape(File.join(Gem.bindir, "bundle")),
+      "install", "--gemfile", Shellwords.escape(gemfile.to_s)
+    ].join(" ")
+
+    "#{bundle} --local || #{bundle}"
+  end
+
   postinstall do
     install_gem("rspec", ">= 3.13")
     install_gem("bundler")
   end
 
+  # Runs the suite's specs.
+  #
+  # If the suite ships a Gemfile its gems are installed first, and if it ships a
+  # setup-recipe.rb that recipe is applied with chef-apply to put the machine
+  # into a known state.
+  #
+  # @raise [RuntimeError] if a setup recipe is present but chef-apply is not
+  #   installed, since running the specs against an unprepared machine would
+  #   produce misleading failures
+  # @return [void]
   def test
     rspec_path = suite_path("rspec").to_s
 
@@ -43,21 +111,19 @@ class Busser::RunnerPlugin::Rspec < Busser::RunnerPlugin::Base
         # to the internet-enabled version. It's a speed optimization.
         banner("Bundle Installing..")
         ENV["PATH"] = [ENV["PATH"], Gem.bindir, RbConfig::CONFIG["bindir"]].join(File::PATH_SEPARATOR)
-        bundle_exec = "#{File.join(RbConfig::CONFIG["bindir"], "ruby")} " +
-          "#{File.join(Gem.bindir, "bundle")} install --gemfile #{gemfile_path}"
-        run("#{bundle_exec} --local || #{bundle_exec}")
+        run(self.class.bundle_install_command(gemfile_path))
       end
 
       if File.exist?(setup_file)
         unless File.exist?("/opt/chef/bin/chef-apply")
-          raise "You have a chef setup file at #{setup_file}, but /opt/chef/bin/chef-apply does not if exist"
+          raise "You have a chef setup file at #{setup_file}, but /opt/chef/bin/chef-apply does not exist"
         end
 
-        run("/opt/chef/bin/chef-apply #{setup_file}")
+        run(self.class.chef_apply_command(setup_file))
       end
 
       runner = File.expand_path(File.join(File.dirname(__FILE__), "..", "rspec", "runner.rb"))
-      run_ruby_script!("#{runner} -I #{rspec_path} -I #{rspec_path}/lib #{rspec_path}")
+      run_ruby_script!(self.class.runner_command(runner, rspec_path))
     end
   end
 end

data/spec/busser/runner_plugin/rspec_spec.rb

@@ -0,0 +1,87 @@
+require_relative "../../spec_helper"
+
+require "rbconfig"
+require "shellwords"
+require "busser/runner_plugin/rspec"
+
+describe Busser::RunnerPlugin::Rspec do
+  describe ".runner_command" do
+    let(:cmd) do
+      Busser::RunnerPlugin::Rspec.runner_command("/gems/busser-rspec/lib/busser/rspec/runner.rb",
+        "/opt/busser/suites/rspec")
+    end
+
+    it "runs the runner script against the suite" do
+      _(Shellwords.split(cmd)).must_equal [
+        "/gems/busser-rspec/lib/busser/rspec/runner.rb",
+        "-I", "/opt/busser/suites/rspec",
+        "-I", "/opt/busser/suites/rspec/lib",
+        "/opt/busser/suites/rspec"
+      ]
+    end
+
+    # Documented behaviour: spec_helper.rb is required without a relative path,
+    # which only works while the suite is on the load path.
+    it "puts the suite and its lib directory on the load path" do
+      _(Shellwords.split(cmd).each_cons(2).select { |flag, _| flag == "-I" }.map(&:last))
+        .must_equal ["/opt/busser/suites/rspec", "/opt/busser/suites/rspec/lib"]
+    end
+
+    it "quotes a suite path containing spaces" do
+      cmd = Busser::RunnerPlugin::Rspec.runner_command("/a/runner.rb", "/tmp/my tests/rspec")
+
+      _(Shellwords.split(cmd)).must_equal [
+        "/a/runner.rb",
+        "-I", "/tmp/my tests/rspec",
+        "-I", "/tmp/my tests/rspec/lib",
+        "/tmp/my tests/rspec"
+      ]
+    end
+
+    it "accepts a Pathname suite" do
+      cmd = Busser::RunnerPlugin::Rspec.runner_command("/a/runner.rb", Pathname.new("/b/rspec"))
+      _(Shellwords.split(cmd).last).must_equal "/b/rspec"
+    end
+  end
+
+  describe ".chef_apply_command" do
+    it "applies the setup recipe with chef-apply" do
+      cmd = Busser::RunnerPlugin::Rspec.chef_apply_command("/suite/setup-recipe.rb")
+
+      _(Shellwords.split(cmd))
+        .must_equal ["/opt/chef/bin/chef-apply", "/suite/setup-recipe.rb"]
+    end
+
+    it "quotes a path containing spaces" do
+      cmd = Busser::RunnerPlugin::Rspec.chef_apply_command("/tmp/my tests/setup-recipe.rb")
+
+      _(Shellwords.split(cmd).last).must_equal "/tmp/my tests/setup-recipe.rb"
+    end
+  end
+
+  describe ".bundle_install_command" do
+    let(:cmd) { Busser::RunnerPlugin::Rspec.bundle_install_command("/suite/Gemfile") }
+
+    it "invokes bundler through the running Ruby rather than PATH" do
+      first, second = Shellwords.split(cmd).first(2)
+
+      _(first).must_equal File.join(RbConfig::CONFIG["bindir"], "ruby")
+      _(second).must_equal File.join(Gem.bindir, "bundle")
+    end
+
+    it "names the suite's Gemfile explicitly" do
+      _(Shellwords.split(cmd)).must_include "/suite/Gemfile"
+    end
+
+    it "falls back from the local attempt to a networked one" do
+      _(cmd).must_include "--local || "
+      _(cmd.scan("--gemfile").length).must_equal 2
+    end
+
+    it "quotes a Gemfile path containing spaces" do
+      cmd = Busser::RunnerPlugin::Rspec.bundle_install_command("/tmp/my tests/Gemfile")
+
+      _(Shellwords.split(cmd.split(" || ").first)).must_include "/tmp/my tests/Gemfile"
+    end
+  end
+end

data/spec/spec_helper.rb

@@ -0,0 +1,2 @@
+require "minitest/autorun"
+require "mocha/minitest"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: busser-rspec
 version: !ruby/object:Gem::Version
-  version: 0.8.0
+  version: 0.8.1
 platform: ruby
 authors:
 - Adam Jacob
@@ -38,9 +38,9 @@ files:
 - ".markdownlint.yaml"
 - ".release-please-manifest.json"
 - ".rubocop.yml"
-- ".tailor"
 - ".yamllint"
 - CHANGELOG.md
+- CONTRIBUTING.md
 - Gemfile
 - LICENSE
 - README.md
@@ -55,6 +55,8 @@ files:
 - lib/busser/runner_plugin/rspec.rb
 - release-please-config.json
 - renovate.json
+- spec/busser/runner_plugin/rspec_spec.rb
+- spec/spec_helper.rb
 homepage: https://github.com/test-kitchen/busser-rspec
 licenses:
 - Apache-2.0

data/.tailor

@@ -1,4 +0,0 @@
-Tailor.config do |config|
-  config.formatters "text"
-  config.file_set 'lib/**/*.rb'
-end