Depending on how they’re written, minitests should run equally well on
Windows and Linux. We have a few cross-platform cookbooks that we test
with minitest-chef-handler … and many more that are primarily intended
for Linux and don’t get as much attention on other platforms. However, I
do have counterparts who work regularly in Windows and they don’t seem to
have any problems writing and running minitests for Windows. So I can
personally attest that the minitest handler does run on Windows.
I haven’t dug too deeply into Serverspec (it’s hard enough convincing
people to adopt Chef and testing methodologies, let alone throwing a whole
new independent framework into the mix…), but my limited tire-kicking and
code review suggests that Serverspec relies on SSH or local execution, but
is otherwise a Ruby implementation relying on Specinfra, which claims to
have Windows support.
So “on paper” Serverspec should work for you.
I really wish Windows were easier to test / work with from a non-Windows
host. Pondering the idea of having a dedicated Parallels (Virtuozzo) host
to spin up and converge Windows containers (running minitests, of course).
From a really distant “I haven’t installed this anywhere yet” perspective,
it seems like a good idea.
On Fri, Apr 11, 2014 at 5:18 PM, Alex Myasnikov <
I am looking to automate functional checks post chef-client run on a
windows node. For instance is IIS running? configured up to spec? needed
files/dirs., web.config settings are in place? etc…
Is minitest chef handler a viable approach for windows, any examples out
there for windows? Or does it depend case by case, assertion by assertion?
Are there any alternative methods? Checked Opscode’s IIS cookbook and
didn’t see any explicit tests.
Serverspec seems to be for *nux only.
Thank you in advance.