https://github.com/petems/cucumber-puppet.example

Example project of cucumber-puppet usage
https://github.com/petems/cucumber-puppet.example

Last synced: 1 day ago
JSON representation

Example project of cucumber-puppet usage

• Host: GitHub
• URL: https://github.com/petems/cucumber-puppet.example
• Owner: petems
• Created: 2011-12-09T21:43:01.000Z (almost 13 years ago)
• Default Branch: master
• Last Pushed: 2013-10-23T11:37:06.000Z (almost 11 years ago)
• Last Synced: 2024-07-02T10:07:16.139Z (3 months ago)
• Language: Ruby
• Homepage:
• Size: 108 KB
• Stars: 15
• Watchers: 5
• Forks: 6
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Cucumber-Puppet Example

[![Build Status](https://travis-ci.org/petems/cucumber-puppet.example.png?branch=master)](https://travis-ci.org/petems/cucumber-puppet.example)

An example puppet project, using cucumber-puppet.

Have a look at the commit log to see how the project evolves.

There are several points to take away:

* use an overarching catalog policy to specify generic behaviour of all

  catalogs

* use module specific features to describe those parts of your manifests or

  templates, that contain logic

* use module specific features to describe custom extensions like functions

* write high level feature files, don't get yourself hung up on details

  * as a corollary, steps are hardly reusable, they should be tailored to your

    specific situation

* keep your step implementations short, just write the code you wish you had

* the bulk of the work should be done by custom helper methods

Are you wondering how to accomplish some task with cucumber-puppet? Do you have

any feedback on the work presented here? Just open an issue and let me know!