mparker17 / chef-drupal Goto Github PK

There seems to be a number of ways to test chef recipes.

Some tools:

• knife cookbook test — static analysis of code for syntax errors — but doesn't work for code not already in a full Chef configuration directory.
• ruby -wc $filename — static analysis of code for syntax errors
• Rubocop — static analysis of ruby code for syntax errors, style best-practices.
• Foodcritic — static analysis of Cookbook code for best practices.
• ChefSpec — run the cookbook locally with Chef without actually configuring the machine.
• KitchenCI aka Test Kitchen — run tests on an environment set up by this cookbook.
• Travis CI — pull it all together so code is automatically tested when it gets committed.

It looks like Opscode uses KitchenCI internally.

Some potentially-useful articles:

• Unit Testing Chef Cookbooks
• Test-Driven Chef Cookbooks with Test Kitchen
• Testing Your Automation by Nathen Harvey

I need to:

• Find the best way to set up testing
• Set it up

People looking to quickly get started with Drupal will want to install Drupal from a release tarball.

Version 1.1.0 should support a use-case I don't normally have anymore: installing Drupal through a core release tarball.

Add a README file with helpful information.
Add a metadata.rb to identify the cookbook to Chef.

People using a distribution will want to install Drupal by cloning an installation profile to /tmp and using Drush Make to build a Drupal installation.

Core developers and users of popular hosting systems that use Git internally, like Pantheon and Acquia, will want to be able to clone Drupal with git.