inspec/kitchen/rake-tests/kitchen.yml

driver:
  name: docker

platforms:
- name: ubuntu-18.04
  driver_config:
    image: ubuntu:18.04
    platform: ubuntu
    provision_command:
      - curl -L https://omnitruck.chef.io/install.sh | sudo bash -s -- -P inspec
      - apt-get -y install build-essential
    require_chef_omnibus: false
    volume: <%= File.expand_path("../..", File.dirname(__FILE__)) %>:/inspec

provisioner:
  name: shell

verifier:
  name: shell
  remote_exec: true
  command: cd /inspec && PATH=/opt/inspec/embedded/bin:$PATH bundle exec rake test

suites:
- name: default
Add kitchen rake testing I'd suggest starting to structure kitchen testing like this with a directory and subdirs to keep the kitchen testing gems out of the root Gemfile entirely. This still mounts the root dir in /inspec so the root Gemfile is still what you're running the rake tests against. By having an extra layer of subdirs, then you can split up different use cases like the rake-testing vs. the audit cookbook testing. Otherwise it'll be a mess of having to manage different kitchen.yml files that require way too many different drivers/provisioners/verifiers 2019-05-15 22:30:26 +00:00			`driver:`
			`name: docker`

			`platforms:`
			`- name: ubuntu-18.04`
			`driver_config:`
			`image: ubuntu:18.04`
			`platform: ubuntu`
			`provision_command:`
			`- curl -L https://omnitruck.chef.io/install.sh \| sudo bash -s -- -P inspec`
			`- apt-get -y install build-essential`
			`require_chef_omnibus: false`
			`volume: <%= File.expand_path("../..", File.dirname(__FILE__)) %>:/inspec`

			`provisioner:`
			`name: shell`

			`verifier:`
			`name: shell`
			`remote_exec: true`
			`command: cd /inspec && PATH=/opt/inspec/embedded/bin:$PATH bundle exec rake test`

			`suites:`
			`- name: default`