rspec-puppet | RSpec tests for your Puppet manifests | UI Testing library

Until recently, the Puppetlabs_spec_helper actually behaved the way you wanted it to, i.e. the fixtures directory was not cleaned unless all the tests pass.

I notice this patch here changed that behaviour. For what it's worth, I also don't agree with that change.

Anyway, if you want the old behaviour, you could:

1. Use an earlier version of Puppetlabs_spec_helper.

2. Define a custom spec task.

3. Or just run bundle exec rake spec_prep spec_standalone.

4. Or if you just want to run the tests in one file, run bundle exec rake spec_prep; bundle exec rspec spec/somefile_spec.rb --fail-fast. (The --fail-fast option is useful when debugging failing tests and it causes rspec to abort on the first failure.)

To define a custom spec task with the old behaviour, add this to your Rakefile:

Remove or fix your pre_condition, it isn't generating a valid Puppet manifest:

There isn't really much support in rspec-puppet for this, as a class test parameters list is generated from the :params assuming only strings (or nested hashes/arrays etc. containing strings) or a couple of permitted symbol values used almost literally, :undef and :default. It doesn't have a way of passing in resource references.

A workaround exists that lets you put literal content into a manifest though, by passing an object that responds to the inspect method. For example, in your spec_helper.rb:

So, after further research, I found that the problem was not related to my code, files or configuration but with a problem with Rubygems.

Bottomline, I had to follow this link and manually update the certificate.

It looks like ruby wasn't able to connect to the server to check for dependencies of the gems I was requiring.