[chef] Re: Re: Strainer vs Rake

[Josiah Kiehl < >]

Many people do not put their cookbooks in chef-repo, opting to create a new repository for each cookbook like the opscode-cookbooks organization on GitHub, and use Chef Spec to test their cookbooks: https://github.com/sethvargo/chefspec

On Tue, Apr 22, 2014 at 6:19 AM, Stewart, Curtis < " target="_blank"> > wrote:

I just wanted to bump this thread to see if there were any new thoughts.

Curtis

On Apr 15, 2014, at 11:56 AM, Stewart, Curtis < " target="_blank"> > wrote:

We’re currently working with a chef-repo and I’m wondering what the better solution is, using a Rake or Strainer for testing.

I’m aware that cookbook-repo’s are preferred, but we’re unable to go that route at this time.

Possible options:

• Repo-level Rakefile
• Individual Rakefiles per cookbook directory
• Both repo-level (global testing) and cookbook-level (single cookbook tests) Rakefiles
• Repo-level Strainerfile
• Individual Strainerfiles per cookbook directory

I can see advantages for each, wondering what other’s thoughts/preferences/experiences are.

Additional comments/thoughts:

• Strainer provides complete isolation by copying a cookbook to a $SANDBOX directory.
• Repo-level Rakefile would run all tests (including running specs in parallel with parallel_specs)

Thanks!

Curtis