explore testing and ci

[jacksingleton]

• what level of testing would make sense? ServerSpec seems quite low level could we do some broader acceptance testing?
• can we use travis or snap-ci to test this? will we need to spin up a separate VM?

[iflowfor8hours]

When picking this up, perhaps figuring out how to use vagrant-cachier plugin to speed up vagrant provisioning would be good too. Currently the debian basebox is missing the vbox guest additions because of licencing issues, so the plugin doesn't work.

[iflowfor8hours]

I got as far as running the cryptsetup until it blows up. Strange because the tests for the cryptsetup role itself seem to pass. However the author is doing a ton of magic bootstrapping through a pretty intense ansible testing framework he wrote. I haven't tried it with our role yet.

[conorsch]

For local testing of Ansible roles, I highly recommend molecule with serverspec unit tests for system state. Writing serverspec tests leaves the door open for a trivial port to inspec, which isn't quite production-ready yet, but has the huge benefit of trivial retargeting, meaning you can verify over SSH transport (vagrant, prod) or local (perfect for CI).

[iflowfor8hours]

Nice find. Usally I'm aware of tools in this space, but I had never
heard of molecule. It sounds like what I need. I'll give it a go
tonight. I haven't used serverspec in a long time but might be useful in
this case. Test kitchen always seems so heavyweight compared to what I
want to be doing.

On Fri, Mar 4, 2016, at 04:28 PM, Conor wrote:

For local testing of Ansible roles, I highly recommend molecule[1]
with serverspec unit tests for system state. Writing serverspec tests
leaves the door open for a trivial port to inspec[2], which isn't
quite production-ready yet, but has the huge benefit of trivial
retargeting, meaning you can verify over SSH transport (vagrant, prod)
or local (perfect for CI).

— Reply to this email directly or view it on GitHub[3].

Links:

1. http://molecule.readthedocs.org/en/master/
2. https://www.chef.io/blog/2015/11/04/the-road-to-inspec/
3. explore testing and ci #10 (comment)