On Tue, Jul 2, 2013 at 12:47 AM, Simon Marechal <[email protected]>wrote:
> > I don't think these tools cover the basic testing needs, at least not > mine. I only knew about the first, which is mainly useful to write > standalone module specific tests, and is pretty slow. The second seems to > require a puppet master, so is not really usable for "pre-commit" testing. > It is also quite likely it is not faster than the Puppet built-in compiler. > > I believe rspec-puppet is a good tool for public module development and > that puppet-spec might be good for compliance related tasks, but they are > not suited for interactive usage. This is probably a controversial opinion > though, because they probably are much used, and I don't think my own > testing framework (language-puppet) is really used by many people ;) > I feel like it's worth mentioning https://github.com/puppetlabs/rspec-system-puppet as well, which is intended for post catalog testing. I waver back and forth on where it makes sense to test but there's a lot of benefit to testing your modules after they've been applied to various distributions instead of trying to test the catalogs directly. It's going to be even slower than rspec-puppet so doesn't really cover the kind of lightweight testing you're getting from lpuppet but it has proven to be fairly useful for me while playing around with it. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
