Skip to content
Example project of cucumber-puppet usage
Ruby Puppet
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
data More changes...
features template refactoring: step 4
gemfiles Use apprasil for different versions of Puppet
manifests
modules/dhcp More changes...
.gitignore More changes...
.ruby-version Currently only working for Puppet 2.6.18
.travis.yml Use apprasil for different versions of Puppet
Appraisals Use apprasil for different versions of Puppet
Gemfile
README.md
Rakefile Use apprasil for different versions of Puppet

README.md

Cucumber-Puppet Example

Build Status

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!

Something went wrong with that request. Please try again.