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
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
## Windows support
Serverspec is now providing a limited support for Microsoft Windows.
If you want to test Windows based machines you need to set the target host's OS explicitly in your `spec/spec_helper.rb`
For local testing (equivalent to the Exec option in Linux/Unix systems) simply do:
```ruby
require 'serverspec'
set :backend, :cmd
set :os, :family => 'windows'
```
For remote testing you have to configure Windows Remote Management in order to communicate to the target host:
```ruby
require 'serverspec'
require 'winrm'
set :backend, :winrm
set :os, :family => 'windows'
user = <username>
pass = <password>
endpoint = "http://#{ENV['TARGET_HOST']}:5985/wsman"
if Gem::Version.new(WinRM::VERSION) < Gem::Version.new('2')
winrm = ::WinRM::WinRMWebService.new(endpoint, :ssl, :user => user, :pass => pass, :basic_auth_only => true)
winrm.set_timeout 300 # 5 minutes max timeout for any operation
else
opts = {
user: user,
password: pass,
endpoint: endpoint,
operation_timeout: 300,
no_ssl_peer_verification: false,
}
winrm = ::WinRM::Connection.new(opts)
end
Specinfra.configuration.winrm = winrm
```
For how to configure the guest to accept WinRM connections and the different authentication mechanisms check the Microsoft WinRM documentation and verify the ones that are supported by [WinRb/WinRM](https://github.com/WinRb/WinRM).
###RSpec Examples for windows target hosts
```ruby
describe file('c:/windows') do
it { should be_directory }
it { should be_readable }
it { should_not be_writable.by('Everyone') }
end
describe file('c:/temp/test.txt') do
it { should be_file }
it { should contain "some text" }
end
describe package('Adobe AIR') do
it { should be_installed}
end
describe service('DNS Client') do
it { should be_installed }
it { should be_enabled }
it { should be_running }
it { should have_start_mode("Manual") }
end
describe port(139) do
it { should be_listening }
end
describe user('some.admin') do
it { should exist }
it { should belong_to_group('Administrators')}
end
describe group('Guests') do
it { should exist }
end
describe group('MYDOMAIN\Domain Users') do
it { should exist }
end
describe command('& "ipconfig"') do
its(:stdout) { should match /IPv4 Address(\.| )*: 192\.168\.1\.100/ }
end
describe windows_registry_key('HKEY_USERS\S-1-5-21-1319311448-2088773778-316617838-32407\Test MyKey') do
it { should exist }
it { should have_property('string value') }
it { should have_property('binary value', :type_binary) }
it { should have_property('dword value', :type_dword) }
it { should have_value('test default data') }
it { should have_property_value('multistring value', :type_multistring, "test\nmulti\nstring\ndata") }
it { should have_property_value('qword value', :type_qword, 'adff32') }
it { should have_property_value('binary value', :type_binary, 'dfa0f066') }
end
describe windows_feature('Minesweeper') do
it{ should be_installed }
it{ should be_installed.by("dism") }
it{ should be_installed.by("powershell") }
end
describe iis_website("Default Website") do
it { should exist }
it { should be_enabled }
it { should be_running }
it { should be_in_app_pool "DefaultAppPool" }
it { should have_physical_path "c:/inetpub/wwwroot" }
end
describe iis_app_pool("DefaultAppPool") do
it { should exist }
it { should have_dotnet_version "2.0" }
end
```
###Notes:
* Not all the matchers you are used to in Linux-like OS are supported in Windows, some because of differences between the operating systems (e.g. users and permissions model), some because they haven't been yet implemented.
* All commands in the windows backend are run via powershell, so the output in case of stderr is a pretty ugly xml-like thing. Still it should contain some information to help troubleshooting.
* The *command* type is executed again through powershell, so bear that in mind if you mean to run old CMD windows batch or programs. (i.e run the command using the **Invoke-Expression** Cmdlet, or the **&** Call Operator)
* You may have to change Exectution Policy on the machine at both, machine and user level in order for tests to run: Get-ExecutionPolicy -list|%{set-executionpolicy bypass -scope $_.scope}
|
