rspec-puppet/Gemfile

source :rubygems

puppetversion = ENV.key?('PUPPET_VERSION') ? "= #{ENV['PUPPET_VERSION']}" : ['>= 2.7']
rspecversion = ENV.key?('RSPEC_VERSION') ? "= #{ENV['RSPEC_VERSION']}" : ['>= 2.9']

gem 'rake'
gem 'rspec', rspecversion
gem 'puppet', puppetversion
gem 'puppetlabs_spec_helper'
Have Travis-ci test rspec-puppet automatically 2012-04-05 23:27:33 +00:00			`source :rubygems`

			`puppetversion = ENV.key?('PUPPET_VERSION') ? "= #{ENV['PUPPET_VERSION']}" : ['>= 2.7']`
fix tests for rspec-2.11.0 2012-07-31 15:07:47 +00:00			`rspecversion = ENV.key?('RSPEC_VERSION') ? "= #{ENV['RSPEC_VERSION']}" : ['>= 2.9']`
Have Travis-ci test rspec-puppet automatically 2012-04-05 23:27:33 +00:00
			`gem 'rake'`
fix tests for rspec-2.11.0 2012-07-31 15:07:47 +00:00			`gem 'rspec', rspecversion`
Have Travis-ci test rspec-puppet automatically 2012-04-05 23:27:33 +00:00			`gem 'puppet', puppetversion`
Use puppetlabs_spec_helper to test parser functions Without this patch applied rspec-puppet reaches deep inside of Puppet and uses an unsupported and private interface to obtain functions and scope instances. This is a problem because Puppet Labs considers internal classes such as Puppet::Parser::Scope as private and internal. We change these classes without warning and this is a maintenance issue for third party testing tools. This patch fixes this maintenance problem by using the compatibility layer implemented in the puppetlabs_spec_helper. When we change the internal behavior of private classes such as Puppet::Parser::Scope, we'll update the spec helper module methods to provide a version agnostic way to get instances of these internal objects. As an example, a supported way to get a scope instance is: PuppetlabsSpec::PuppetInternals.scope Instead of the private and unsupported method of: Puppet::Parser::Scope.new This patch introduces a Gem dependency onto the puppetlabs_spec_helper gem. 2012-08-14 23:25:09 +00:00			`gem 'puppetlabs_spec_helper'`