[chef] Re: Re: Re: Re: Re: Re: Re: Continuous Integration

[Michael Hale < >]

On Thu, Jul 8, 2010 at 12:36 AM, Chad Woolley 
<
 >
 wrote:
> On Wed, Jul 7, 2010 at 9:14 PM, AJ Christensen 
> <
 >
>  wrote:
>> It seems what we're all really talking about is some kind of BDD framework
>> for Chef cookbooks - unit testing (also related to --noop) has proven
>> unreliable for this kind of thing: you can't mock UNIX.
>> I know there was work done on this in the past - mikehale's chef-bdd
>> project http://github.com/mikehale/chef-bdd for example.
>
> I don't get what that is for.  To only test the filesystem aspects of
> cookbooks?  Does it somehow mock out other calls to run services and
> such?  What about stuff like the hostname reference:
>
> http://github.com/mikehale/chef-bdd/blob/master/features/step_definitions/custom_steps.rb#L17
>
> Too bad there isn't a README...

This code is very much a work in progress, and I haven't made any
progress in awhile. I started out trying to mock everything, but it
was pointed out to me that mocking UNIX is silly. My current thinking
is to combine some cucumber steps like those in the aforementioned
file with vagrant to auto provision a test cloud that matches a
description. So the cucumber might look something like this:

Given I have cluster X
When I have run chef-client on all the nodes
Then I should see "my load balanced website" on "http://example.com";

>