From 5f9ed88471a2aff0db4a90ba4dd7902c07e6a058 Mon Sep 17 00:00:00 2001 From: Gabriel Filion Date: Sat, 24 Jun 2017 23:44:01 -0400 Subject: specs: manually define debian_nextcodename when expected to be used with puppet 4.x when you don't define the debian_nextcodename, compilation fails saying that the variable is unknown. since we have unit tests specifically for this fact's behaviour, we want to stub out the fact's value in other tests so that we can verify the logic of manifests is actually good. --- spec/classes/init_spec.rb | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) (limited to 'spec/classes') diff --git a/spec/classes/init_spec.rb b/spec/classes/init_spec.rb index 9ba554f..a3f19a0 100644 --- a/spec/classes/init_spec.rb +++ b/spec/classes/init_spec.rb @@ -5,14 +5,15 @@ describe 'apt', :type => :class do 'class { "apt": }' end let(:facts) { { - :lsbdistid => 'Debian', - :osfamily => 'Debian', - :operatingsystem => 'Debian', - :debian_release => 'jessie', - :debian_codename => 'jessie', - :lsbdistcodename => 'jessie', - :virtual => 'physical', - :puppetversion => Puppet.version, } } + :lsbdistid => 'Debian', + :osfamily => 'Debian', + :operatingsystem => 'Debian', + :debian_release => 'jessie', + :debian_codename => 'jessie', + :lsbdistcodename => 'jessie', + :debian_nextcodename => 'stretch', + :virtual => 'physical', + :puppetversion => Puppet.version, } } #it { is_expected.to compile.with_all_deps } it { is_expected.to compile } end -- cgit v1.2.3