Yeah, but here you're in reboot_pending_spec.rb and you can test in isolation that when you mix it into a generic class that it behaves correctly.  Then in the recipe_spec.rb you can test that you've mixed it into Chef::Recipe specifically.  And Chemilsky's point in that thread that I sent you is that you should really defined a `shared_examples_for "reboot pending DSL sauce"` that you test in unit/recipe_spec.rb with `it_behaves_like "reboot pending DSL sauce"` and then do the same for Chef::Resource.

And there's an advantage to testing it in a generic class here which is that you know Class.new will not give you a class that implements #reboot_pending?  so that if you mix it in and call `reboot_pending?` the fact that you don't get a NoMethodError exception is sufficient to show that the method was mixed into the class.

Then all of the stuff to setup a Chef::Recipe as a subject and mock things is left in unit/recipe_spec.rb and you don't need to copypasta that stuff into this recipe and change it in two places if the Chef::Recipe code ever changes.