[chef] Re: Testing Cookbooks vs Testing Infrastructure

[Tensibai < >]

I had a discussion with a colleague this morning about this and pointed to Terraform[1].

As we're already using vagrant with a custom provider (for vsphere) we're planning to move toward this path. for now it's just an idea with no feedback but the described way Terraform works sounds interesting to write "plans" to ensure idem-potency for cookbooks (spin up a machine, converge it once, re-converge it, change a parameter somewhere, converge again, ensure expectation are there).

That's what we're aiming to do, launched from jenkins on cookbook commit after usual linting/chefspec test.

I'll try to write something about it if we end up with something functional at end.

Le 2015-04-22 07:40, Torben Knerr a écrit :

Hey everybody,

@jtimberman's recent blog post about test-driven infrastructure with
Chef made me thinking about this again.

All the tools we currently have are focused on cookbook testing, but
we have nothing established for acceptance level infrastructure
testing yet, do we?

I mean specifically:

 * testing from the outside vs from the inside
 * testing multi-vm setups

See also my comment on the original post:
https://www.chef.io/blog/2015/04/21/overview-of-test-driven-infrastructure-with-chef/


What do we have in this space?

Cheers,
Torben