On Mar 31, 3:22 pm, Clay Caviness <ccavin...@gmail.com> wrote: > Well, I'm very interested in testing in general, but it's probably a bit > premature to put it in the style guide if it's not clearly documented what > they are and how they work. No?
Nah, I disagree with that. As far as I'm concerned, our policy is to write a given document as a good document! If that ends up revealing deficiencies elsewhere, we fix those when we can. (In this case, being "good" meant capturing the best practices for module development as understood by our professional services team and others. Leaving out the note about testing would have made it a document about something other than the current best practices.) Anyway, I'm writing a short document about module testing now. If you see other things missing in the documentation, we love getting tickets filed. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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.
