[chef] Re: Re: ChefSpec v3.1.0 hits the shelves

["Wolfe, Eric G" < >]

I played around with this today on my yum-dell 
(https://github.com/atomic-penguin/cookbook-yum-dell) cookbook that I have 
been working on since the yum 3.0 release.

It doesn't seem to be recognizing consumed LWRP resources touched by tests.  
Am I missing some magic syntax keyword, or is that by design/necessity?

Seth Vargo 
<
 >
 wrote:



As promised, I wrote a blog post about the new resource coverage reporter in 
ChefSpec: https://sethvargo.com/chef-recipe-code-coverage/.

Happy reading/cooking/testing!

Seth Vargo
Release Engineer, Opscode
@sethvargo<https://twitter.com/sethvargo>
________________________________
From: Seth Vargo Seth 
Vargo<mailto:
 >
Reply: Seth Vargo 

 <mailto:
 >
Date: December 29, 2013 at 2:57:10 PM
To: 

 
 

 <mailto:
 >
Subject:  ChefSpec v3.1.0 hits the shelves

Ohai Chefs,

I'm happy to announce that I just released ChefSpec v3.1.0. The beta has been 
out for 2 weeks and users have reported very little problems. I made a few 
tiny documentation updates and improved the DSL for interacting with the Chef 
Server.

Changelog<https://github.com/sethvargo/chefspec/blob/master/CHANGELOG.md>, 
Changeset<https://github.com/sethvargo/chefspec/compare/v3.0.2...master>

You can install ChefSpec 3.1.0 by running:

gem install chefspec --version 3.1.0



Or by updating the version in your Gemfile:

gem 'chefspec', '~> 3.1.0'



ChefSpec v3.1.0 builds upon the 3.0.0 series with amazing new features like:

  *   Converging against a "real" Chef Server (Chef Zero) (no need to use 
Chef Solo)
  *   Resource reporting! It's finally here! Although still in primitive 
stages, ChefSpec v3.1.0 performs recipe analysis and generates a resource 
coverage report - perfect for testing you've hit all logic branches in your 
recipes
  *   (Advanced) Cacheable runner courtesy of Juri 
Timošin<https://github.com/DracoAter> for incredibly faster tests if you 
don't need stubbing
  *   Support for Librarian courtesy of Mathias 
Lafeldt<https://github.com/mlafeldt>

Things that are likely to break:

  *   The deprecations module is no longer included by default. If you have 
not yet upgraded from ChefSpec v2.x, you can manually include the module by 
adding require 'chefspec/deprecations' to the top of your spec_helper.
  *   The API for creating a node changed slightly between the last beta and 
this final release.

There are some really cool nerdy things happening under the hood, so I 
encourage you to look at the full diff :).

Look for an upcoming blog series on sethvargo.com about resource reporting 
(coverage) and chef server mode.

Join #chefspec on IRC on freenode

If you have blog posts, publications, or case studies for ChefSpec, please 
ping me.


Seth Vargo
Release Engineer, Opscode
@sethvargo<https://twitter.com/sethvargo>