How Cucumber + Puppet Should be Used
DZone's Guide to
How Cucumber + Puppet Should be Used
Join the DZone community and get the full member experience.
Join For FreeDo you need to strengthen the security of the mobile apps you build? Discover more than 50 secure mobile development coding practices to make your apps more secure.
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/
Check out tips for blazing the way from agile to DevSecOps with security built into your mobile app toolchain.
Like This Article? Read More From DZone
Topics:
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}