busser-rspec 0.7.6 → 0.8.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 7379d7a390cd41afe74d348be6d7713537c260c7
-  data.tar.gz: 4458837da64c1cc71f7e691a3e3f016d5bbfa095
+SHA256:
+  metadata.gz: 217c8f2f4bb8a712f4d69e22c3567334306c9d0e44cdc418c47630ee84660ffe
+  data.tar.gz: cf85c2e7e49b49c74273c9d2f11ee208d3eadead985ff3f9f021a7e35ace6b53
 SHA512:
-  metadata.gz: 25810747e9a2d8f0eebe6d1fd87a4f90ae0fdaa92fc3b2cd1e51452a242daec9a3e7c6fda9cadcff98271a5cefe27881186d4762701696dc1dca93a05f12c02c
-  data.tar.gz: 18d03e1b6968b38506f8cd518fb69f681cceb28547d2315fbd95d0f56226fee1aadd876eb19a6bb8366fcad957b09605253785aabc93b29333fa0536b525a2cf
+  metadata.gz: 677c89b4864b780207555fcfe5b176e172e50c2a77ecdfd8ce8f5723fb0988250c3e9e03bacf3781f3a5486eed4050e8a5a1415288f4f1396eb4bcc239d5bc1c
+  data.tar.gz: a1ed580c340581807850947ee6ce8f391483dd809aa98efb86c7960af31318e468244c63f671948e85540fe98fcf70190dfb966fe5080e3d4d453d3153db64d0

data/.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+---
+name: "Test"
+
+"on":
+  push:
+    branches: [main]
+  pull_request:
+  workflow_dispatch:
+
+# The default token is granted write access to most of the repository.
+# Nothing here needs more than the checkout.
+permissions:
+  contents: read
+
+# Supersede in-flight runs for a branch. Pull requests cancel freely, but
+# pushes to main do not: every commit on main should keep a build of its own.
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+jobs:
+  lint-unit:
+    # Pinned to a commit rather than @main so an upstream edit cannot reach
+    # this repository's CI without a reviewed pull request. The trailing
+    # comment names the release the commit belongs to, which is what lets
+    # Renovate track the pin by version and keep both in step.
+    uses: test-kitchen/.github/.github/workflows/lint-unit.yml@95ef7803cf23aae5ee68593de5b7e0a731c1a929  # v0.4.0
+    with:
+      # This gem requires Ruby 3.2, and so do busser 0.9 and cucumber 11.
+      # Without this the shared workflow would still start a Ruby 3.1 job and
+      # bundler would refuse to resolve there.
+      ruby_versions: '["3.2", "3.3", "3.4", "4.0"]'

data/.github/workflows/pr-title.yml

@@ -0,0 +1,28 @@
+---
+name: "PR Title"
+
+"on":
+  pull_request_target:
+    types: [opened, edited, reopened, synchronize]
+
+permissions:
+  contents: read
+
+jobs:
+  conventional-title:
+    name: "Conventional commit title"
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: read
+    steps:
+      # Pull requests here are squash merged, so the pull request title becomes
+      # the commit subject on main. That makes the title the one place worth
+      # checking: release-please reads those subjects to decide the next
+      # version and to build the changelog.
+      #
+      # pull_request_target is used so the check also runs for pull requests
+      # from forks. No repository code is checked out in this job, so none of
+      # the usual pull_request_target risk applies.
+      - uses: amannn/action-semantic-pull-request@48f256284bd46cdaab1048c3721360e808335d50  # v6.1.1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

data/.github/workflows/publish.yml

@@ -0,0 +1,67 @@
+---
+name: "Release"
+
+"on":
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write        # tag the release and commit the version bump
+      pull-requests: write   # open and update the release pull request
+      packages: write        # push the gem to GitHub Packages
+    steps:
+      # Opens and maintains a release pull request. Merging that pull request
+      # is what actually cuts a release, so every step below is skipped until
+      # release_created is set.
+      - uses: googleapis/release-please-action@45996ed1f6d02564a971a2fa1b5860e934307cf7  # v5.0.0
+        id: release
+        with:
+          token: ${{ secrets.PORTER_GITHUB_TOKEN }}
+
+      - name: Checkout code
+        if: ${{ steps.release.outputs.release_created }}
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+
+      # These two steps are handed publishing credentials, so they are pinned
+      # to a commit rather than a branch. A floating ref would let whoever
+      # controls that branch run code with a token that can push this gem.
+      - name: Publish to GitHub Packages
+        if: ${{ steps.release.outputs.release_created }}
+        uses: actionshub/publish-gem-to-github@86eb0ce1ced1072298bf68776a32a5c9703ad9aa  # v1.0.13
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          owner: ${{ github.repository_owner }}
+
+      - name: Publish to RubyGems
+        if: ${{ steps.release.outputs.release_created }}
+        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/.markdownlint.yaml

@@ -0,0 +1,6 @@
+---
+default: true
+MD004: false
+MD012: false
+MD013: false
+MD024: false

data/.release-please-manifest.json

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

data/.rubocop.yml

@@ -0,0 +1,6 @@
+---
+require:
+  - cookstyle/chefstyle
+
+AllCops:
+  TargetRubyVersion: 3.2

data/.yamllint

@@ -0,0 +1,6 @@
+---
+extends: default
+rules:
+  line-length:
+    max: 256
+    level: warning

data/CHANGELOG.md

@@ -3,6 +3,24 @@
 * 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)
+
+
+### ⚠ BREAKING CHANGES
+
+* Ruby 3.1 and busser releases older than 0.9.0 are no longer supported.
+
+### Features
+
+* require Ruby 3.2 and busser 0.9, adopt release-please ([#22](https://github.com/test-kitchen/busser-rspec/issues/22)) ([144aeb9](https://github.com/test-kitchen/busser-rspec/commit/144aeb9174d2d62597c962b3e75579e5b8c02226))
+
 ## 0.7.5 / 2015-09-17
 
 * Fix bundle install on windows

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

@@ -1,3 +1,21 @@
-source 'https://rubygems.org'
+source "https://rubygems.org"
 
 gemspec
+
+group :cookstyle do
+  gem "cookstyle", ">= 9.0"
+end
+
+group :test do
+  gem "aruba", ">= 2.4"
+  gem "base64", ">= 0.3" # cucumber needs it; not a default gem on Ruby 4.0
+  gem "cucumber", ">= 11.1"
+  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,61 +1,149 @@
-# Busser::RunnerPlugin::Rspec
+# busser-rspec
 
-A Busser runner plugin for Rspec
+[![Gem Version](https://badge.fury.io/rb/busser-rspec.svg)](https://badge.fury.io/rb/busser-rspec)
 
-## Installation and Setup
+A [Busser](https://github.com/test-kitchen/busser) runner plugin that runs
+[RSpec](https://rspec.info) examples as integration tests.
 
-Please read the Busser [plugin usage](plugin_usage) page for more details.
+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.
+
+## Requirements
+
+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.
+
+## 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
+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
 ```
--- [COOKBOOK]
-  `-- test
-     `-- integration
-        `-- default
-           `-- rspec
-              `-- spec_helper.rb
-              `-- Gemfile
+
+### 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.
 
-## How do I ... ?
+### Chef setup
 
-### Change the rspec formatter?
+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.
 
-You may be familar with using the `rspec -f` flag to change the rspec formatter. RSpec also offers a way to set the formatter from your specs:
+### Changing the formatter
+
+`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
 ```
 
-## Development
+## 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
+```
 
-* Source hosted at [GitHub](https://github.com/opscode/busser-rspec)
-* Report issues/questions/feature requests on [GitHub Issues](issues)
+Then put your tests in a `rspec` directory inside the suite:
 
-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:
+```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
+
+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,31 +1,36 @@
 require "bundler/gem_tasks"
-require 'cucumber/rake/task'
-require 'cane/rake_task'
-require 'tailor/rake_task'
-
-Cucumber::Rake::Task.new(:features) do |t|
-  t.cucumber_opts = ['features', '-x', '--format progress']
+require "rake/testtask"
+Rake::TestTask.new(:unit) do |t|
+  t.libs.push "lib"
+  t.test_files = FileList["spec/**/*_spec.rb"]
+  t.verbose = true
 end
 
-desc "Run all test suites"
-task :test => [:features]
+require "cucumber/rake/task"
 
-desc "Run cane to check quality metrics"
-Cane::RakeTask.new do |cane|
-  cane.canefile = './.cane'
+Cucumber::Rake::Task.new(:features) do |t|
+  t.cucumber_opts = ["features", "--format progress", "--fail-fast"]
 end
 
-Tailor::RakeTask.new
+# 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"
 
-desc "Display LOC stats"
-task :stats do
-  puts "\n## Production Code Stats"
-  sh "countloc -r lib"
-  puts "\n## Test Code Stats"
-  sh "countloc -r features"
+  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 quality tasks"
-task :quality => [:cane, :tailor, :stats]
+desc "Run all test suites"
+task test: %i{unit features}
 
-task :default => [:test, :quality]
+task default: [:test]

data/busser-rspec.gemspec

@@ -1,32 +1,30 @@
-# coding: utf-8
-lib = File.expand_path('../lib', __FILE__)
+lib = File.expand_path("lib", __dir__)
 $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require 'busser/rspec/version'
+require "busser/rspec/version"
 
 Gem::Specification.new do |spec|
-  spec.name          = 'busser-rspec'
+  spec.name          = "busser-rspec"
   spec.version       = Busser::Rspec::VERSION
-  spec.authors       = ['Adam Jacob']
-  spec.email         = ['adam@opscode.com']
-  spec.description   = %q{A Busser runner plugin for RSpec}
+  spec.authors       = ["Adam Jacob"]
+  spec.email         = ["adam@opscode.com"]
+  spec.description   = "A Busser runner plugin for RSpec"
   spec.summary       = spec.description
-  spec.homepage      = 'https://github.com/adamhjk/busser-rspec'
-  spec.license       = 'Apache 2.0'
+  spec.homepage      = "https://github.com/test-kitchen/busser-rspec"
+  spec.license       = "Apache-2.0"
 
-  spec.files         = `git ls-files`.split($/)
-  spec.executables   = []
-  spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
-  spec.require_paths = ['lib']
+  spec.required_ruby_version = ">= 3.2"
 
-  spec.add_dependency 'busser'
+  spec.files         = `git ls-files -z`.split("\x0")
+  spec.executables   = []
+  spec.require_paths = ["lib"]
 
-  spec.add_development_dependency 'rspec'
-  spec.add_development_dependency 'chef'
+  spec.metadata = {
+    "bug_tracker_uri" => "#{spec.homepage}/issues",
+    "changelog_uri" => "#{spec.homepage}/blob/main/CHANGELOG.md",
+    "documentation_uri" => "#{spec.homepage}/blob/main/README.md",
+    "homepage_uri" => spec.homepage,
+    "source_code_uri" => spec.homepage,
+  }
 
-  spec.add_development_dependency 'bundler', '~> 1.3'
-  spec.add_development_dependency 'rake'
-  spec.add_development_dependency 'aruba'
-  spec.add_development_dependency 'cane'
-  spec.add_development_dependency 'tailor'
-  spec.add_development_dependency 'countloc'
+  spec.add_dependency "busser", ">= 0.9.0"
 end

data/features/plugin_install_command.feature

@@ -4,8 +4,10 @@ Feature: Plugin install command
   I want to run the postinstall for this plugin
 
   Background:
-    Given a test BUSSER_ROOT directory named "busser-rspec-install"
+    Given a non bundler environment
+    And a test BUSSER_ROOT directory named "busser-rspec-install"
     And a sandboxed GEM_HOME directory named "busser-rspec-gem-home"
+    And this plugin is installed from the working tree
 
   Scenario: Running the postinstall generator
     When I run `busser plugin install busser-rspec --force-postinstall`

data/features/support/env.rb

@@ -1,13 +1,48 @@
-require 'aruba/cucumber'
-require 'busser/cucumber'
+require "fileutils" unless defined?(FileUtils)
+require "rubygems/package"
 
-Before do
-  @aruba_timeout_seconds = 20
+require "aruba/cucumber"
+require "busser/cucumber"
+
+# aruba 2 dropped @aruba_timeout_seconds; setting it in a Before hook is a
+# no-op, which quietly left these commands on aruba's 15 second default.
+# Installing a plugin and its gems into a cold sandbox does not always fit.
+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?
+# The sandboxed features shell out to `busser plugin install <this plugin>`, and
+# two things have to hold for that to exercise this checkout:
+#
+#   * The child has to be free of bundler. RubyGems re-requires bundler/setup
+#     whenever BUNDLER_SETUP is set, and bundler then resets Gem.dir to the
+#     bundle, so busser installs into vendor/bundle rather than the sandboxed
+#     GEM_HOME the features assert against. busser's "a non bundler environment"
+#     step clears that, and has to run before the sandbox is set up.
+#   * The plugin has to already be in that sandbox. Otherwise busser fetches the
+#     last release from RubyGems and runs *its* postinstall, which means CI
+#     silently tests the published gem instead of the code under review.
+#
+# So build the gem from the working tree and install it into the sandbox first.
+Given(/^this plugin is installed from the working tree$/) do
+  root = File.expand_path("../..", __dir__)
+  package = nil
+
+  begin
+    Dir.chdir(root) do
+      spec = Gem::Specification.load(Dir["*.gemspec"].first)
+      package = Gem::Package.build(spec)
+
+      # --ignore-dependencies keeps this from reaching the network: busser and
+      # the rest are already resolvable through the GEM_PATH the sandbox step
+      # leaves in place.
+      installed = system(
+        Gem.ruby, "-S", "gem", "install", "--local", "--no-document",
+        "--ignore-dependencies", package, out: File::NULL
+      )
+      raise "could not install #{package} into #{ENV["GEM_HOME"]}" unless installed
+    end
+  ensure
+    FileUtils.rm_f(File.join(root, package)) if package
+  end
 end

data/features/test_command.feature

@@ -4,8 +4,10 @@ Feature: Test command
   I want my tests to run when the rspec runner plugin is installed
 
   Background:
-    Given a test BUSSER_ROOT directory named "busser-rspec-test"
+    Given a non bundler environment
+    And a test BUSSER_ROOT directory named "busser-rspec-test"
     And a sandboxed GEM_HOME directory named "busser-rspec-gem-home"
+    And this plugin is installed from the working tree
     When I successfully run `busser plugin install busser-rspec --force-postinstall`
     Given a suite directory named "rspec"
 

data/lib/busser/rspec/runner.rb

@@ -1,5 +1,4 @@
 #!/usr/bin/env ruby
-# -*- encoding: utf-8 -*-
 #
 # Author:: HIGUCHI Daisuke (<d-higuchi@creationline.com>)
 #
@@ -17,7 +16,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-require 'bundler/setup'
-require 'rspec/core'
+require "bundler/setup"
+require "rspec/core"
 
 exit RSpec::Core::Runner.run(ARGV)

data/lib/busser/rspec/version.rb

@@ -1,4 +1,3 @@
-# -*- encoding: utf-8 -*-
 #
 # Author:: HIGUCHI Daisuke (<d-higuchi@creationline.com>)
 #
@@ -18,9 +17,10 @@
 
 module Busser
 
+  # Namespace for the RSpec Busser runner plugin.
   module Rspec
 
     # Version string for the Rspec Busser runner plugin
-    VERSION = "0.7.6"
+    VERSION = "0.8.1".freeze
   end
 end

data/lib/busser/runner_plugin/rspec.rb

@@ -1,4 +1,3 @@
-# -*- encoding: utf-8 -*-
 #
 # Author:: HIGUCHI Daisuke (<d-higuchi@creationline.com>)
 #
@@ -16,48 +15,115 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-require 'busser/runner_plugin'
-require 'rubygems'
+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")
+    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
+    rspec_path = suite_path("rspec").to_s
 
     setup_file = File.join(rspec_path, "setup-recipe.rb")
 
     Dir.chdir(rspec_path) do
 
       # Referred from busser-serverspec
-      gemfile_path = File.join(rspec_path, 'Gemfile')
-      if File.exists?(gemfile_path)
+      gemfile_path = File.join(rspec_path, "Gemfile")
+      if File.exist?(gemfile_path)
         # Bundle install local completes quickly if the gems are already found locally
         # it fails if it needs to talk to the internet. The || below is the fallback
         # 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}")
+        banner("Bundle Installing..")
+        ENV["PATH"] = [ENV["PATH"], Gem.bindir, RbConfig::CONFIG["bindir"]].join(File::PATH_SEPARATOR)
+        run(self.class.bundle_install_command(gemfile_path))
       end
 
-      if File.exists?(setup_file)
-        if !File.exists?("/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"
+      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 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/release-please-config.json

@@ -0,0 +1,15 @@
+{
+  "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
+  "bootstrap-sha": "ec6c35fd8840d47bd7c30c9a7a425bee46f5282b",
+  "packages": {
+    ".": {
+      "package-name": "busser-rspec",
+      "changelog-path": "CHANGELOG.md",
+      "release-type": "ruby",
+      "include-component-in-tag": false,
+      "version-file": "lib/busser/rspec/version.rb",
+      "bump-minor-pre-major": true,
+      "bump-patch-for-minor-pre-major": true
+    }
+  }
+}

data/renovate.json

@@ -0,0 +1,8 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": [
+    "config:recommended",
+    "helpers:pinGitHubActionDigests",
+    ":semanticCommits"
+  ]
+}

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,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: busser-rspec
 version: !ruby/object:Gem::Version
-  version: 0.7.6
+  version: 0.8.1
 platform: ruby
 authors:
 - Adam Jacob
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2015-09-28 00:00:00.000000000 Z
+date: 2026-08-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: busser
@@ -16,126 +16,14 @@ dependencies:
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.9.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
       - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: rspec
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: chef
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: bundler
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.3'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.3'
-- !ruby/object:Gem::Dependency
-  name: rake
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: aruba
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: cane
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: tailor
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: countloc
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.9.0
 description: A Busser runner plugin for RSpec
 email:
 - adam@opscode.com
@@ -143,11 +31,16 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".cane"
+- ".github/workflows/ci.yml"
+- ".github/workflows/pr-title.yml"
+- ".github/workflows/publish.yml"
 - ".gitignore"
-- ".tailor"
-- ".travis.yml"
+- ".markdownlint.yaml"
+- ".release-please-manifest.json"
+- ".rubocop.yml"
+- ".yamllint"
 - CHANGELOG.md
+- CONTRIBUTING.md
 - Gemfile
 - LICENSE
 - README.md
@@ -160,11 +53,20 @@ files:
 - lib/busser/rspec/runner.rb
 - lib/busser/rspec/version.rb
 - lib/busser/runner_plugin/rspec.rb
-homepage: https://github.com/adamhjk/busser-rspec
+- 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
-metadata: {}
-post_install_message: 
+- Apache-2.0
+metadata:
+  bug_tracker_uri: https://github.com/test-kitchen/busser-rspec/issues
+  changelog_uri: https://github.com/test-kitchen/busser-rspec/blob/main/CHANGELOG.md
+  documentation_uri: https://github.com/test-kitchen/busser-rspec/blob/main/README.md
+  homepage_uri: https://github.com/test-kitchen/busser-rspec
+  source_code_uri: https://github.com/test-kitchen/busser-rspec
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -172,20 +74,15 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '0'
+      version: '3.2'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.2.2
-signing_key: 
+rubygems_version: 3.5.9
+signing_key:
 specification_version: 4
 summary: A Busser runner plugin for RSpec
-test_files:
-- features/plugin_install_command.feature
-- features/plugin_list_command.feature
-- features/support/env.rb
-- features/test_command.feature
+test_files: []

data/.tailor

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

data/.travis.yml

@@ -1,11 +0,0 @@
-language: ruby
-
-rvm:
-- 2.0.0
-- 1.9.3
-- 1.9.2
-- ruby-head
-
-matrix:
-  allow_failures:
-  - rvm: ruby-head