From 969b8f3200104bfce891135a486ed4e66f86d85d Mon Sep 17 00:00:00 2001 From: Florian Bruhin Date: Wed, 4 Oct 2017 08:55:33 +0200 Subject: [PATCH] Fix test_configcommands on Python 3.5 looks like assert_called_once() was introduced in 3.6 --- tests/unit/config/test_configcommands.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tests/unit/config/test_configcommands.py b/tests/unit/config/test_configcommands.py index a0b646893..c4b188fb8 100644 --- a/tests/unit/config/test_configcommands.py +++ b/tests/unit/config/test_configcommands.py @@ -19,6 +19,7 @@ """Tests for qutebrowser.config.configcommands.""" import logging +import unittest.mock import pytest from PyQt5.QtCore import QUrl, QProcess @@ -305,7 +306,7 @@ class TestEdit: mock = mocker.patch('qutebrowser.config.configcommands.editor.' 'ExternalEditor._start_editor', autospec=True) commands.config_edit(no_source=True) - mock.assert_called_once() + mock.assert_called_once_with(unittest.mock.ANY) @pytest.fixture def patch_editor(self, mocker, config_tmpdir, data_tmpdir): @@ -328,7 +329,7 @@ class TestEdit: commands.config_edit() - mock.assert_called_once() + mock.assert_called_once_with(unittest.mock.any) assert not config_stub.val.content.javascript.enabled def test_error(self, commands, config_stub, patch_editor, message_mock,