DevOps Zone is brought to you in partnership with:

Mitch Pronschinske is the Lead Research Analyst at DZone. Researching and compiling content for DZone's research guides is his primary job. He likes to make his own ringtones, watches cartoons/anime, enjoys card and board games, and plays the accordion. Mitch is a DZone Zone Leader and has posted 2576 posts at DZone. You can read more from them at their website. View Full User Profile

How Cucumber + Puppet Should be Used

12.14.2011
| 11121 views |
  • submit to reddit

Prompted by Patrick Dubois' recent blog post on Puppet unit testing, Nikolay Sturm followed up with a blog related to the cucumber-puppet on discussion that ensued.  He's got an example project up on GitHub for your viewing pleasure.  Here's three points on how Nikolay thinks cucumber-puppet should be used:

  • On a global scale, use a catalog policy to ensure all your node catalogs obey the same basic rules.
  • Use module specific features to specify behaviour in manifests, templates, custom functions, etc.
  • Don’t repeat your manifests in your features, however. There’s no value in it.
    --Nikolay Sturm

Sturm says that he believes the project is not meant to be proscriptive about the steps definitions for various scenarios, but instead it should be used to to provide a basic level of definitions for the steps that you already use.

 

If you have any suggestions for the example project, send them his way.
 

Source:  http://blog.nistu.de/2011/12/11/an-example-project-using-cucumber-puppet/