From ac3e72da3258f8e3396b4aa3cc648cf8d4e38bc2 Mon Sep 17 00:00:00 2001 From: Hunter Haugen Date: Wed, 12 Apr 2017 11:19:32 -0700 Subject: [PATCH] (maint) Stub fact exists call with argument passed I can't replicate what's going on, but I wonder if the stub is being bypassed and the actual underlying debian filesystem is being hit. The timestamps returned by the unit test are from just before the unit test ran. --- spec/unit/facter/apt_update_last_success_spec.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/unit/facter/apt_update_last_success_spec.rb b/spec/unit/facter/apt_update_last_success_spec.rb index 14bc3ab..4de608d 100644 --- a/spec/unit/facter/apt_update_last_success_spec.rb +++ b/spec/unit/facter/apt_update_last_success_spec.rb @@ -7,7 +7,7 @@ describe 'apt_update_last_success fact' do describe 'on Debian based distro which has not yet created the update-success-stamp file' do it 'should have a value of -1' do Facter.fact(:osfamily).stubs(:value).returns 'Debian' - File.stubs(:exists?).returns false + File.expects(:exists?).with('/var/lib/apt/periodic/update-success-stamp').returns false is_expected.to eq(-1) end end -- 2.45.2