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

On 28 August 2015 at 14:00, Ilja Bobkevic <[email protected]> wrote:

> 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
>
>
> Den onsdag 5 augusti 2015 kl. 18:44:30 UTC+2 skrev Garrett Honeycutt:
>>
>> On 8/4/15 3:37 PM, Peter Berghold 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...
>> >
>>
>> 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
>>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/e4cf0fd7-71e7-4c22-8ac4-616a88fff6d5%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/e4cf0fd7-71e7-4c22-8ac4-616a88fff6d5%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAN4dctrjm%2B5Giv_pX%3DWyLTd0s8Rum0ECQJh7o5Um4t1d-Zwi-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to