Over a million developers have joined DZone.

How Cucumber + Puppet Should be Used

· DevOps Zone

The DevOps zone is brought to you in partnership with Sonatype Nexus. The Nexus suite helps scale your DevOps delivery with continuous component intelligence integrated into development tools, including Eclipse, IntelliJ, Jenkins, Bamboo, SonarQube and more. Schedule a demo today

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/



The DevOps zone is brought to you in partnership with Sonatype Nexus. Use the Nexus Suite to automate your software supply chain and ensure you're using the highest quality open source components at every step of the development lifecycle. Get Nexus today

Topics:

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}