[chef] Re: Re: Re: Re: Re: automated testing of cookbooks

[Peter Norton < >]

+1.  And I'd like to have options for other languages.  It doesn't
need to be in the chef DSL, but there should be a best practice to a
callout from a recipe to test and to run a test in any language, and
to be able to close the loop and confirm that the test completed and
know its status.  We'd like chef to be part of a deployment system and
this is important to controlling the lifecycle of the deployment.

-Peter

On Wed, Nov 23, 2011 at 11:24 AM, Burkholder, Peter
<
 >
 wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>>>>
>>>>>
>>>>> I noticed that Bryan Berry suggested "cookbook testing" as a topic for 
>>>>> the
>>>>> community summit.
>>>>>
>>>>>    "Cookbook testing and how to automate it, esp. for opscode/cookbooks"
>>>>>
>>>
> The variety of ways suggested so far to skin this cat seems to makes it 
> seem like a ripe topic for the summit.  As a new Chef adopter I'd like to 
> see a convergence upon best practice before trying four different 
> approaches, then building my own.
>
> P.
> - --
> Peter Burkholder | Sr. System Administrator (consultant)
> AARP | Digital Strategy & Operations | 601 E Street NW | Washington, DC 
> 20049
> 
 
>  | aim: peterbtech | w: 202-434-3530 | c: 202-344-7129
>  For optimal efficiency, I check email at 2-hour intervals during the 
> workday
>  (except when on-call). Please use IM or phone to contact me for urgent 
> matters
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
>
> iEYEARECAAYFAk7NHkgACgkQLvy74DZcgeSIegCgywRX0tNuj5u7qZhzPfpQLnDl
> H2oAoNXEOO/HPC3NODQVSruGKR52muLn
> =vNa2
> -----END PGP SIGNATURE-----
>