On Thu, Mar 31, 2011 at 11:29, Dan Bode <d...@puppetlabs.com> wrote:
>
>
> On Thu, Mar 31, 2011 at 8:20 AM, Clay Caviness <ccavin...@gmail.com>wrote:
>
>> Reading through the recently published style guide, I see
>> http://docs.puppetlabs.com/guides/style_guide.html#tests saying:
>>
>> "All manifests should have a corresponding test manifest in the module’s
>> tests directory."
>>
>
> the idea is to have maintain basic tests written in Puppet for all of your
> manifests in a module.
>
>
they can serve not only as basic smoke tests, but also as a reference for
> example code of how a class/define should be used.
>
>
But when/how are these tests run?
> the simplest tests would be:
>
> class{ 'foo': }
>
> more complicated tests would involve specifying required dependencies and
> parameters.
>
>
Are there examples and documentation on how they should work available
anywhere?
>
>> Is there any documentation on how these work? I couldn't find anything in
>> the documentation on puppetlabs or any mention in release notes.
>>
>> --
>> 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.
>>
>
>
--
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.
