Based on an original idea from apenney, this gem provides a method of running your rspec-puppet tests against the facts for all your supported operating systems (provided by facterdb. This simplifies unit testing because you don't need to specify the facts yourself.
If you're using Bundler to manage gems in your module repository, install rspec-puppet-facts by adding it to the Gemfile.
- Add the following line to your
Gemfile:
gem 'rspec-puppet-facts', '~> 1.7', :require => false- Run
bundle install.
If you're not using Bundler, install the rspec-puppet-facts manually.
- On the command line, run:
$ gem install rspec-puppet-factsAfter the gem is installed (using either method), make the gem available to rspec by adding the following lines in your spec/spec_helper.rb file. Place the lines after require 'rspec-puppet' and before the RSpec.configure block, if one exists.
require 'rspec-puppet-facts'
include RspecPuppetFactsTo determine which facts to run your tests against, rspec-puppet-facts checks your module's metadata.json to find out what operating systems your module supports. The metadata.json file is located in the root of your module. To learn more about this file, see Puppet's metatdata documentation.
By default, rspec-puppet-facts provides the facts only for x86_64 architecture. However, you can override this default and the supported operating system list by passing a hash to on_supported_os in your tests. This hash must contain either or both of the following keys:
:hardwaremodels- An array of hardware architecture names, as strings.:supported_os- An array of hashes representing the operating systems. Note: the keys of these hashes must be strings'operatingsystem'- The name of the operating system, as a string.'operatingsystemrelease'- An array of version numbers, as strings.
This is particularly useful if your module is split into operating system subclasses. For example, if you had a class called myclass::debian that you wanted to test against Debian 6 and Debian 7 on both x86_64 and i386 architectures, you could write the following test:
require 'spec_helper'
describe 'myclass::debian' do
test_on = {
:hardwaremodels => ['x86_64', 'i386'],
:supported_os => [
{
'operatingsystem' => 'Debian',
'operatingsystemrelease' => ['6', '7'],
},
],
}
on_supported_os(test_on).each do |os, facts|
let (:facts) { facts }
it { is_expected.to compile.with_all_deps }
end
endUse the on_supported_os iterator to loop through all of your module's supported operating systems. This allows you to simplify your tests and remove a lot of duplicate code.
Each iteration of on_supported_os provides two variables to your tests. (In the code examples below, these variables are specified by the values between the pipe (|) characters.)
- The first value is the name of the fact set. This is made from the values of the operatingsystem, operatingsystemmajrelease, and architecture facts separated by dashes (for example, 'debian-7-x86_64').
- The second value is the facts for that combination of operating system, release, and architecture.
For example, previously, you might have written a test that specified Debian 7 and Red Hat 6 as the supported modules:
require 'spec_helper'
describe 'myclass' do
context "on debian-7-x86_64" do
let(:facts) do
{
:osfamily => 'Debian',
:operatingsystem => 'Debian',
:operatingsystemmajrelease => '7',
...
}
end
it { is_expected.to compile.with_all_deps }
...
end
context "on redhat-6-x86_64" do
let(:facts) do
{
:osfamily => 'RedHat',
:operatingsystem => 'RedHat',
:operatingsystemmajrelease => '6',
...
}
end
it { is_expected.to compile.with_all_deps }
...
end
...
endWith on_supported_os iteration, you can rewrite this test to loop over each of the supported operating systems without explicitly specifying them:
require 'spec_helper'
describe 'myclass' do
on_supported_os.each do |os, facts|
context "on #{os}" do
let(:facts) do
facts
end
it { is_expected.to compile.with_all_deps }
...
# If you need any to specify any operating system specific tests
case facts[:osfamily]
when 'Debian'
...
else
...
end
end
end
endUse on_supported_os in the same way for your type and provider unit tests.
Specifying each operating system:
require 'spec_helper'
describe 'mytype' do
context "on debian-7-x86_64" do
let(:facts) do
{
:osfamily => 'Debian',
:operatingsystem => 'Debian',
:operatingsystemmajrelease => '7',
}
end
it { should be_valid_type }
...
end
context "on redhat-7-x86_64" do
let(:facts) do
{
:osfamily => 'RedHat',
:operatingsystem => 'RedHat',
:operatingsystemmajrelease => '7',
}
end
it { should be_valid_type }
...
end
endLooping with on_supported_os iterator:
require 'spec_helper'
describe 'mytype' do
on_supported_os.each do |os, facts|
context "on #{os}" do
let(:facts) do
facts
end
it { should be_valid_type }
...
# If you need to specify any operating system specific tests
case facts[:osfamily]
when 'Debian'
...
else
...
end
...
end
end
endAs with testing manifests, types, or providers, on_supported_os iteration simplifies your function unit tests.
Specifying each operating system:
require 'spec_helper'
describe 'myfunction' do
context "on debian-7-x86_64" do
let(:facts) do
{
:osfamily => 'Debian',
:operatingsystem => 'Debian',
...
}
end
it { should run.with_params('something').and_return('a value') }
...
end
context "on redhat-7-x86_64" do
let(:facts) do
{
:osfamily => 'RedHat',
:operatingsystem => 'RedHat',
...
}
end
it { should run.with_params('something').and_return('a value') }
...
end
endLooping with on_supported_os iterator:
require 'spec_helper'
describe 'myfunction' do
on_supported_os.each do |os, facts|
context "on #{os}" do
let(:facts) do
facts
end
it { should run.with_params('something').and_return('a value') }
...
end
end
endBy adding custom fact values, you can:
- Override fact values
- Include additional facts in your tests.
- Add global custom facts for all of your unit tests
- Add custom facts to only certain operating systems
- Add custom facts to all operating systems except specific operating systems
- Create dynamic values for custom facts by setting a lambda as the value.
To override fact values and include additional facts in your tests, merge values with the facts hash provided by each iteration of on_supported_os.
require 'spec_helper'
describe 'myclass' do
on_supported_os.each do |os, facts|
context "on #{os}" do
# Add the 'foo' fact with the value 'bar' to the tests
let(:facts) do
facts.merge({
:foo => 'bar',
})
end
it { is_expected.to compile.with_all_deps }
...
end
end
endSet global custom fact values in your spec/spec_helper.rb file so that they are automatically available to all of your unit tests using on_supported_os.
Pass the fact name and value to the add_custom_fact function:
require 'rspec-puppet'
require 'rspec-puppet-facts'
include RspecPuppetFacts
# Add the 'concat_basedir' fact to all tests
add_custom_fact :concat_basedir, '/doesnotexist'
RSpec.configure do |config|
# normal rspec-puppet configuration
...
endTo add custom facts for only certain operating systems, set confine with the operating system as a string value:
add_custom_fact :root_home, '/root', :confine => 'redhat-7-x86_64'To add custom facts for all operating systems except specific ones, set exclude with the operating system as a string value:
add_custom_fact :root_home, '/root', :exclude => 'redhat-7-x86_64'In addition to the static fact values shown in the previous examples, you can create dynamic values.
To do this, pass a lambda as the value for the custom fact. The lambda is passed the same values for operating system name and fact values that your tests are provided by on_supported_os.
add_custom_fact :root_home, lambda { |os,facts| "/tmp/#{facts['hostname']}" }For most cases, there is no change to how you run your tests. Running rake spec will run all the tests against the facts for all the supported operating systems.
If you want to run the tests against the facts for specific operating systems, you can provide a filter in the SPEC_FACTS_OS environment variable and only the supported operating systems whose name starts with the specified filter will be used.
SPEC_FACTS_OS='ubuntu-14' rake specWhen no facts are available for the specific facter/operating system combination, the library will fall back to facts from earlier versions of the requested operating system, to allow testing to continue when new versions of facter are released. Set SPEC_FACTS_STRICT=yes to instead trigger a failure.