I’ve found a similar issue reported and a workaround is explained
https://github.com/freerange/mocha/issues/445#issuecomment-644944003
use kwargs vs **kwargs, then kwargs will be a Hash which you can use in your assertion and no warnings will be generated…
Applying the workaround suggested makes failing specs green.
https://github.com/yahonda/discourse/commit/356f15b02cb4a0bb869d19adf2a2018d07ee79bf
$ git diff main
diff --git a/spec/lib/backup_restore/shared_context_for_backup_restore.rb b/spec/lib/backup_restore/shared_context_for_backup_restore.rb
index 2ff78176ea..0fbc8ade15 100644
--- a/spec/lib/backup_restore/shared_context_for_backup_restore.rb
+++ b/spec/lib/backup_restore/shared_context_for_backup_restore.rb
@@ -33,7 +33,7 @@ shared_context "shared stuff" do
end
def expect_db_migrate
- Discourse::Utils.expects(:execute_command).with do |env, *command, **options|
+ Discourse::Utils.expects(:execute_command).with do |env, *command, options|
env["SKIP_POST_DEPLOYMENT_MIGRATIONS"] == "0" &&
env["SKIP_OPTIMIZE_ICONS"] == "1" &&
env["DISABLE_TRANSLATION_OVERRIDES"] == "1" &&
$
I am happy to open a pull request.