Good afternoon all, I've played a bit with rspec puppet lately trying to use it in a sane way, checking if the module's logic is correctly applied rather than if Puppet does what it's supposed to do. But I'm really new to rspec and might miss some important points.
My efforts are for the moment dedicated to a single "simple" openssh module, in order to make it a good starting point and reference for my future modules. You can find them here: https://github.com/example42/puppet-openssh/blob/master/spec/classes/openssh_spec.rb consider that the module has not custom functions or defines, so the tests are only for the main openssh class (which actually provides quite a bunch of parameters that affect the provided resources). My question is: do you think that's a good approach for using rspec-puppet? Given the linked output (and the relevant class) can you recommend better style / tests / approaches? On a side note, personally, if I had to choose, I would actually prefer a testing methodology that checks the actual result of a module when applied on the target system rather than a "catalogue based approach" (as rspec or cucumber puppet ones) but still I think they can coexist, if used properly (more ramblings on this and on the whole logic behind that prototype openssh class is here: http://www.example42.com/?q=NextGen ) . But am I using them (well, rspec in this case) properly? Thank in advance for any advice, Al -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/_NQWEIOHF8sJ. 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.
