On Mon, Jan 21, 2013 at 5:06 AM, Gavin Williams <[email protected]> wrote:
> Afternoon all > > Following a bit more research and reading, I've made a start on the test > framework, as I think this is the biggest blocker to being able to happily > publish the module... > > Great! Testing all to often gets given short shrift. > Have pushed my first set of commits to > Git<https://github.com/fatmcgav/fatmcgav-netapp/commits/rspec-tests>- Am > using a combination of > Puppetlabs_spec_helper<http://puppetlabs.com/blog/the-next-generation-of-puppet-module-testing/>and > a support script I pulled from the puppetlabs-f5 > > <https://github.com/fatmcgav/puppetlabs-f5/blob/master/spec/support/shared_type_examples_spec.rb>module, > with a bit of tweaking... > > Before I push on too much, I wanted to get peoples opinions on if this is > the right way of doing it, or if there is a better/quicker/more scalable > way that could save me time? > > My understanding of this is that you are following the standard way of doing this. Providing feedback to us and helping us make the experience better would be great. I think using git and github is a good way to make sure that what you are doing is accessible to others. Using the puppetlabs spec helper should make testing the module with puppet possible. I'd like to know what we can do to make it seamless and easy, though. > So, any comments welcome. > And as always, thank-you in advance for any responses. > > Cheers > Gavin > > On Friday, 18 January 2013 18:02:39 UTC, Gavin Williams wrote: >> >> Evening all >> >> As some of you are probably aware, I've been working on a NetApp network >> device module to Puppet. >> The module has reached that point whereby it ticks most of the boxes that >> we needed it for internally, and so it's probably time to start looking at >> doing a release to the community, so that can get feedback, any missing >> features, bugs etc... >> >> So I've been drawing up a mental list of things to do to get to release >> point... >> First I think is documentation... Although the code is reasonably well >> documented, got nothing for the types as yet... >> Secondly, need to fix the config file up... Currently it's expecting one >> in /var/lib/puppet/devices/[**device]/, probably want to get those in a >> better location and manageable as part of the module... >> Thirdly, and I think this is going to be most difficult, is a module >> testing... Currently, there's nothing... :( >> >> So, anything I've missed? And any pointers on where to start, especially >> with testing... >> >> Cheers >> Gavin >> >> P.s. For anyone who wants to look at the latest code, it's available >> here: >> https://github.com/fatmcgav/**fatmcgav-netapp<https://github.com/fatmcgav/fatmcgav-netapp> >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-dev/-/qGr7gM4bslwJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
