title: ChefSpec should not test included recipe
body: <p>I have built a cookbook for installing Jenkins CI. It uses the <code>key</code> and <code>repository</code> resources from the <code>yum</code> cookbook, so I end up with the following recipe:</p>
  
  <pre><code>yum_key "RPM-GPG-KEY-jenkins" do
    url "http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key"
    action :add
  end
  
  yum_repository "jenkins" do
    description "Jenkins-CI 3rd party repository"
    url "http://pkg.jenkins-ci.org/redhat"
    key "RPM-GPG-KEY-jenkins"
    action :add
  end
  </code></pre>
  
  <p>When I include this recipe in another recipe:</p>
  
  <pre><code>include_recipe 'sp_jenkins::default'
  </code></pre>
  
  <p>and I test this with the following ChefSpec test</p>
  
  <pre><code>it 'includes the `sp_jenkins::default` recipe' do
    expect(chef_run).to include_recipe('sp_jenkins::install')
  end
  </code></pre>
  
  <p>my ChefSpec test fails with the following output:</p>
  
  <pre><code>NameError:
    Cannot find a resource for yum_key on chefspec version 0.6.1
  </code></pre>
  
  <p>(I'm not sure why it says version 0.6.1, <code>gem list</code> tells me it's using 3.0.2)</p>
  
  <p>The <code>sp_jenkins</code> cookbook does depend on the <code>yum</code> cookbook (metadata.rb), and runs fine, however, the cookbook I'm currently writing does not depend on the <code>yum</code> cookbook and therefore doesn't have the <code>yum_key</code> and <code>yum_repository</code> methods available. </p>
  
  <p>Is there a way to prevent ChefSpec from 'descending' into included recipes/cookbooks and just test the current cookbook?</p>