Puppet Module spec testing

[Peter Berghold]

Is there a newer set of documents on doing Spec testing of Puppet modules than this link?  

https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing

I am running into a brick wall getting this to work so I have to assume I'm doing something wrong...

[Martin Alfke]

Hi Peter,

On 04 Aug 2015, at 21:37, Peter Berghold <salty....@gmail.com> wrote:

> Is there a newer set of documents on doing Spec testing of Puppet modules than this link?
> https://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing
>

> I am running into a brick wall getting this to work so I have to assume I'm doing something wrong…

This should still be valid documentation.
It only refers to unit testing.
For acceptance testing you should take a look on beaker.

hth,
Martin

[Gareth Rushgrove]

If you could post a test case I'd be happy to take a look.

My experience is starting from a working example is useful, shameless
self promotion I know but, the puppet module skeleton should run a set
of unit tests out of the box:
https://github.com/garethr/puppet-module-skeleton

Even if you don't use the skeleton you should be able to get the tests
running at least and then port to your own module.

Gareth


> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAArvnv14GJ0v6Ef0rS4KAcrOf1C%3DUiu%3DpM%2BsnJcxjsptqeipCQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



--
Gareth Rushgrove
@garethr

devopsweekly.com
morethanseven.net
garethrushgrove.com

[Tehmasp Chaudhri]

I've got something similar I built a while ago (and need to update again since I'm back in the Puppet world).

Magnum: https://github.com/tehmaspc/magnum

It will help you create a new module dir with a bunch of puppet tools setup for you - including rspec-puppet for spec testing and serverspec for integration spec testing w/ virtualbox/vagrant.

[Garrett Honeycutt]

Hi Peter,

Take a look at the spec tests[1] in my vim module. It shows how to test
for multiple OS's and how to handle parameters and their validation. The
module itself is simple in that it only handles three resources and a
handful of parameters.

Here's a link[2] to a tutorial I gave last year at LOADays in Antwerp.
This[3] is the vagrant environment we used, though I'm not confident
that it will still work today without some tweaks.

[1] -
https://github.com/ghoneycutt/puppet-module-vim/blob/master/spec/classes/init_spec.rb

[2] - http://www.slideshare.net/gh/20140406-loa-daystddwithpuppettutorial

[3] - https://github.com/ghoneycutt/learnpuppet-tdd-vagrant

Best regards,
-g

--
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658

[Ilja Bobkevic]

Hi,

You're welcome to checkout our modules as well at https://github.com/unibet/. For instance https://github.com/unibet/puppet-vagrant.

Some details about our testing mechanics:

1. rake used to manage the project. See https://github.com/unibet/puppet-vagrant/blob/master/Rakefile

2. puppet-librarian used to prepare fixtures (i.e. dependencies). See https://github.com/unibet/puppet-vagrant/blob/master/Puppetfile and https://github.com/unibet/puppet-vagrant/blob/master/.fixtures.yml

3. rspec used for unit testing. See https://github.com/unibet/puppet-vagrant/tree/master/spec

4. test-kitchen used for integration tests. See https://github.com/unibet/puppet-vagrant/blob/master/.kitchen.yml and https://github.com/unibet/puppet-vagrant/tree/master/test/integration

5. Travis is set to release modules automatically if tests are passing. See https://github.com/unibet/puppet-vagrant/blob/master/.travis.yml

Usual command sequence is:

1. git clone

2. bundle install

3. Make changes

4. rake # no arguments = default task = spec and lint

5. kitchen test # no arguments = all suites

6. commit/push

Let me know if you have any questions.

// Ilja

[Walid]

Hi Ilja,

Any reason you went with test-kitchen as opposed to beaker? i am trying to find a comparision between the two and where one fits better?  as i am going to work with Ansible too i see that learning one tool that would work both in Ansible, and Puppet is a plus, however i am interested to know if one is testing Puppet environments only what are merits and cons of test-kitchen vs. Beaker, given that beaker seems to have matured more since the last year, our toolset will involve bare-metal "ssh", vagrant/libvirt, and docker.

Best regards,

Walid 

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e4cf0fd7-71e7-4c22-8ac4-616a88fff6d5%40googlegroups.com.