Fixed `stub_feature_flag behavior` for `disabled?` flags.

Previous code would not work with `disabled?` because that method would
send two parameters (second always `nil`) which we are not mocking.

Instead of mock yet another state, I decide to fix it where it belongs.

1 files changed, 2 insertions, 1 deletions

diff --git a/spec/services/projects/update_service_spec.rb b/spec/services/projects/update_service_spec.rb
index 2409be80cec..bc8bda1000e 100644
--- a/spec/services/projects/update_service_spec.rb
+++ b/spec/services/projects/update_service_spec.rb
@@ -262,6 +262,7 @@ describe Projects::UpdateService do
         context 'when hashed storage is enabled' do
           before do
             stub_application_setting(hashed_storage_enabled: true)
+            stub_feature_flags(disable_hashed_storage_upgrade: false)
           end
 
           it 'migrates project to a hashed storage instead of renaming the repo to another legacy name' do
@@ -275,7 +276,7 @@ describe Projects::UpdateService do
 
           context 'when disable_hashed_storage_upgrade feature flag is enabled' do
             before do
-              expect(Feature).to receive(:enabled?).with(:disable_hashed_storage_upgrade) { true }
+              stub_feature_flags(disable_hashed_storage_upgrade: true)
             end
 
             it 'renames the project without upgrading it' do