On Tue, Nov 23, 2010 at 12:26 AM, donavan <dona...@desinc.net> wrote: > On Nov 22, 3:21 pm, "russell.fulton" <russell.ful...@gmail.com> wrote: >> Over the last few weeks I have several times felt the need to test out >> some small snippets of puppet code without having to have them in my >> live system. >> >> At the moment I am doing all my testing by fiddling with file on the >> puppet master and then invoking puppet on one of the clients. There >> must be a better way :) > > I suggest taking a look at 'cucumber-puppet'[1]. I'm primarily using > it to test catalog compilation, but you can inspect individual > resources as well. > RI also has some great tools to testing and comparing[2] catalogs. You > can compare changes before you actually apply to 'new' catalog to the > clients.
I've always found it immensely useful to just use standalone puppet manifests (in modules or otherwise) with the ability to set variables by using FACTER_* environment variables. FACTER_somevariable="somevalue" puppet apply -v /tmp/test.pp You can get an awful lot of testing done really quickly like this. FACTER_somevariable gets exposed as $somevariable in the manifests. I'm pretty sure RI has covered this in his posts, but it's how I generally do the first stage of testing, the "does this actually work like this?" stage. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
