Jump to: navigation, search

Difference between revisions of "Puppet/Unit testing"

(retire page)
 
Line 1: Line 1:
 +
'''These docs are outdated, but kept here for historical reasons and search access. To view the latest docs, please refer to http://docs.openstack.org/developer/puppet-openstack-guide/'''
 +
 +
<strike>
 
The best reference for getting started with rspec-puppet can be found [http://rspec-puppet.com/ here].
 
The best reference for getting started with rspec-puppet can be found [http://rspec-puppet.com/ here].
  
Line 12: Line 15:
 
This relies on the file .fixtures.yaml to install all of the external module required for testing.
 
This relies on the file .fixtures.yaml to install all of the external module required for testing.
 
The urls in this file use the git:// protocol, so this may need to be updated if you are behind a proxy.
 
The urls in this file use the git:// protocol, so this may need to be updated if you are behind a proxy.
 +
</strike>

Latest revision as of 23:29, 18 May 2016

These docs are outdated, but kept here for historical reasons and search access. To view the latest docs, please refer to http://docs.openstack.org/developer/puppet-openstack-guide/

The best reference for getting started with rspec-puppet can be found here.

Running local tests

The following command can invoked from any if the modules' directories to run their rspec puppet tests. It assumes that both bundler as well as rubygems (and ruby) are already installed on the system.

mkdir vendor
export GEM_HOME=vendor
bundle install
bundle exec rake spec

This relies on the file .fixtures.yaml to install all of the external module required for testing. The urls in this file use the git:// protocol, so this may need to be updated if you are behind a proxy.