A Busser runner plugin for Serverspec
Branch: master
Clone or download
tyler-ball Merge pull request #59 from test-kitchen/ruby_eol
Ruby < 2.3 is long EOLed, stop supporting it
Latest commit 3adfc6d Feb 12, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
features update for serverspec v2, closes #13 Oct 5, 2014
.cane let mute cane Line is >80 characters Mar 30, 2015
.gitignore ignore vendor Jan 22, 2016
.travis.yml Requiring ruby >= 2.3 at gem level Jan 17, 2019
CHANGELOG.md v0.5.10 Aug 12, 2016
CONTRIBUTING.md You should use Kitchen::Verifier::Shell + Serverspec Mar 2, 2016
Gemfile first commit May 22, 2013
LICENSE update copyright Jan 25, 2014
README.md Update badges Jun 14, 2018
Rakefile Revert "temporary disable tailor test, ref: turboladen/tailor#160" Oct 16, 2014
busser-serverspec.gemspec Don't pin bundler because thats an anti-pattern Feb 12, 2019



Gem Version Build Status Code Climate

A Busser runner plugin for Serverspec

Installation and Setup

Please read the Busser plugin usage page for more details.


Please put test files into [COOKBOOK]/test/integration/[SUITES]/serverspec/

`-- test
    `-- integration
        `-- default
            `-- serverspec
                |-- Gemfile
                |-- localhost
                |   `-- httpd_spec.rb
                `-- spec_helper.rb

Gemfile is optional. You can specify installing Serverspec version and install gems you need.


File Matching

Globbing pattern to match files is "serverspec/*/*_spec.rb". You need to use "_spec.rb" (underscore), not "-spec.rb" (minus).

Specify Serverspec version

If you have to specify Serverspec version, you can use Gemfile. Example Gemfile:

source 'https://rubygems.org'
gem 'serverspec', '< 2.0'

Serverspec backend

It runs on a target server for testing after ssh log in it. So you need to specify set :backend, :exec not set :backend, :ssh (Serverspec v2). If you use Serverspec v1, you need to specify include SpecInfra::Helper::Exec not include SpecInfra::Helper::Ssh.


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:

  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


Created and maintained by HIGUCHI Daisuke (d-higuchi@creationline.com)


Apache 2.0 (see LICENSE)