busser-minitest

A Busser runner plugin that runs minitest tests as integration tests.

Busser installs minitest on the machine under test during postinstall, then runs the suite's minitest directory against it. Both minitest styles work — classic Minitest::Test subclasses and the describe/it spec syntax.

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.

Ruby 3.2 or newer, and busser 0.9.0 or newer. The plugin installs minitest 6.0 or newer on the machine under test.

Busser installs the plugin for you when Test Kitchen runs the suite, so there is usually nothing to do. To install it by hand:

busser plugin install busser-minitest

Put your tests in the minitest directory of a suite:

test
`-- integration
    |-- default             # suite name
    |   `-- minitest
    |       |-- Gemfile         # optional
    |       `-- test_default.rb
    `-- foo
        `-- minitest
            `-- foo_spec.rb

Files are collected recursively, and only names matching test_*.rb or *_spec.rb are run — so helpers named anything else are safe to keep alongside.

Classic style:

require "minitest/autorun"

class TestFoobar < Minitest::Test
  def test_the_file_was_created
    assert File.exist?("/usr/local/foobar.txt")
  end
end

Spec style:

require "minitest/autorun"

describe "foobar::default" do
  it "creates foobar.txt" do
    _(File.exist?("/usr/local/foobar.txt")).must_equal true
  end
end

Expectations must be wrapped in _(). The bare form — File.exist?("...").must_equal true — was removed in minitest 6 and will raise NoMethodError. Minitest::Unit::TestCase was removed back in minitest 5; use Minitest::Test.

If a Gemfile is present in the suite directory, it is bundle installed before the run, which is how you pull in extra assertion libraries or anything else your tests need. The install is attempted with --local first and falls back to the network.

This is how most people run it, and it needs no Busser commands of your own. Select the verifier in kitchen.yml:

verifier:
  name: busser

suites:
  - name: default

Then put your tests in a minitest directory inside the suite:

test/integration/default/minitest/test_default.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.

If the suite files do not match what this plugin looks for, the run prints one line and exits 0:

-----> Running minitest test suite

No tests ran, and nothing said so. Work through these in order:

1. Is the directory named minitest? That name alone selects this plugin. minitests/, tests/ or anything else is not picked up.
2. Do the filenames match? Only test_*.rb and *_spec.rb are run, searched recursively -- 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.

Bug reports and pull requests are welcome. See CONTRIBUTING.md for how to set up the project, run the test suite, and format your commits.

Apache License 2.0. See LICENSE.

Originally created by Fletcher Nichol.