1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
### Specifying facts
By default, the test environment contains only the `hostname`, `domain`, and
`fqdn` facts (determined by the FQDN of the test node). Additional facts can be
specified as a hash of values using `let(:facts)`.
{% highlight ruby %}
let(:facts) { {'operatingsystem' => 'Debian', 'ipaddress' => '192.168.0.1'} }
{% endhighlight %}
Facts may be expressed as a value (shown in the previous example) or
a structure. Fact keys may be expressed as symbols or strings, and will be
converted to a lower case string to align with the Facter standard.
{% highlight ruby %}
let(:facts) do
{
'os' => {
'family' => 'RedHat',
'release' => {
'major' => '7',
'minor' => '1',
'full' => '7.1.1503',
}
}
}
end
{% endhighlight %}
These facts will be merged into the default facts (if set), with these values
taking precedence over the default fact values in the event of a conflict.
If have nested RSpec contexts to test the behaviour of different fact
values, you can partially override the parent facts by merging the changed
facts into `super()` in your `let(:facts)` block.
{% highlight ruby %}
describe 'My::Class' do
let(:facts) do
{
'operatingsystem' => 'Debian',
'role' => 'default',
}
end
context 'with role => web' do
let(:facts) do
super().merge({ 'role' => 'web' })
end
it { should compile }
end
end
{% endhighlight %}
<div class="callout-block callout-info">
<div class="icon-holder"><i class="fa fa-info-circle"></i></div>
<div class="content">
A common pattern is to use <a href="https://github.com/mcanevet/rspec-puppet-facts">rspec-puppet-facts</a> to automatically populate the facts for a specified operating system. Please read the <a href="https://github.com/mcanevet/rspec-puppet-facts/blob/master/README.md">rspec-puppet-facts documentation</a> for more information.
</div>
</div>
### Specifying trusted facts
When testing with Puppet >= 4.3, the trusted facts hash will have the standard
trusted facts (`certname`, `domain`, and `hostname`) populated based on the
node name. Those elements can only be set with the `let(:node)`, not with this
structure.
By default, the test environment contains no custom trusted facts (usually
obtained from certificate extensions) and found in the `extensions` key. If the
manifest being tested depends on the values from specific custom certificate
extensions, they can be specified as a hash using `let(:trusted_facts)`.
{% highlight ruby %}
let(:trusted_facts) { {'pp_uuid' => '012345670-ABCD', 'some' => 'value'} }
{% endhighlight %}
These trusted facts will be merged into the default trusted facts (if set),
with these values taking precedence over the default trusted facts in the event
of a conflict.
If have nested RSpec contexts to test the behaviour of different trusted fact
values, you can partially override the parent trusted facts by merging the
changed facts into `super()` in your `let(:trusted_facts)` block.
{% highlight ruby %}
describe 'My::Class' do
let(:trusted_facts) do
{
'some_common_param' => 'value'
'role' => 'default',
}
end
context 'with role => web' do
let(:trusted_facts) do
super().merge({ 'role' => 'web' })
end
it { should compile }
end
end
{% endhighlight %}
|
