gistfile1.rb

# In default.rb from cookbook being tested
# node.run_state['reboot'] = true

it "flags system to reboot" do
  chef_run.node.run_state['reboot'].should_be true
end

https://www.relishapp.com/rspec/rspec-expectations/v/2-11/docs/built-in-matchers/be-matchers

it "flags system to reboot" do
  chef_run.node.run_state['reboot'].should be_true
end

it "flags system to reboot" do
  chef_run.node.run_state['reboot'].should be
end

it "flags system to reboot" do
  puts chef_run.node.run_state.inspect
end

$ rspec
{:template_cache=>{}, :seen_recipes=>{"foo::default"=>true}, :seen_attributes=>{}, "reboot"=>true}

https://github.com/retr0h/cookbook-sol

emopop:sol(master)% rspec

{:template_cache=>{}, :seen_recipes=>{"sol::default"=>true, "reboot-handler"=>true, "chef_handler"=>true}, :seen_attributes=>{}}

Hi John,

This is because the run_state is modified within a ruby_block. Chefspec treats ruby_block resources the same as any other resource - it doesn't actually apply the resource.

If you specifically want to converge a resource you can do something like the following (there is probably a nicer way of expressing this):

chef_run.resources.find{|r| r.name == 'setting reboot flag'}.old_run_action(:create) 

Awesome! I owe you a beer! :)

That works. Thanks much for your help. I feel like I'm cheating a bit.
It's nice to know my 'update-grub' execute is the one making the call to the 'setting reboot flag' resource.

Maybe, there is no good way to test that.

With modern versions of ChefSpec the following works:
chef_run.find_resource(:ruby_block, 'my ruby_block name').old_run_action(:create)