This spec was setting a Mocha expectation on a method that gets cached globally - so the method isn't called if the class has already been used in another test.
This pattern appears in several other specs; I'm inclined to remove them, especially in the cases where we only have one provider anyway. Does anyone know of a reason not to yank them out? Signed-off-by: Jesse Wolfe <[email protected]> --- spec/unit/other/selinux.rb | 6 ------ 1 files changed, 0 insertions(+), 6 deletions(-) diff --git a/spec/unit/other/selinux.rb b/spec/unit/other/selinux.rb index 3e39afc..4c052e4 100644 --- a/spec/unit/other/selinux.rb +++ b/spec/unit/other/selinux.rb @@ -27,9 +27,6 @@ end describe Puppet::Type.type(:selboolean), " when manipulating booleans" do before :each do - provider_class = Puppet::Type::Selboolean.provider(Puppet::Type::Selboolean.providers[0]) - Puppet::Type::Selboolean.expects(:defaultprovider).returns provider_class - @bool = Puppet::Type::Selboolean.new( :name => "foo", :value => "on", @@ -56,9 +53,6 @@ end describe Puppet::Type.type(:selmodule), " when checking policy modules" do before :each do - provider_class = Puppet::Type::Selmodule.provider(Puppet::Type::Selmodule.providers[0]) - Puppet::Type::Selmodule.expects(:defaultprovider).returns provider_class - @module = Puppet::Type::Selmodule.new( :name => "foo", :selmoduledir => "/some/path", -- 1.6.5 -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
