[tests] Refactor setting up complex I/O mocking for modules

Modules now only have to have a single setup/teardown line in their code
to fully set up the I/O part of a test.
This commit is contained in:
Tobi-wan Kenobi 2017-03-05 13:01:28 +01:00
parent 69dceca7d0
commit 00849aa4fa
5 changed files with 35 additions and 77 deletions

View file

@ -6,33 +6,18 @@ import mock
import tests.mocks as mocks
from bumblebee.config import Config
from bumblebee.input import I3BarInput, LEFT_MOUSE
from bumblebee.input import LEFT_MOUSE
from bumblebee.modules.cpu import Module
class TestCPUModule(unittest.TestCase):
def setUp(self):
self._stdin, self._select, self.stdin, self.select = mocks.epoll_mock("bumblebee.input")
self.popen = mocks.MockPopen()
mocks.setup_test(self, Module)
self._psutil = mock.patch("bumblebee.modules.cpu.psutil")
self.psutil = self._psutil.start()
self.config = Config()
self.input = I3BarInput()
self.engine = mock.Mock()
self.engine.input = self.input
self.input.need_event = True
self.module = Module(engine=self.engine, config={ "config": self.config })
for widget in self.module.widgets():
widget.link_module(self.module)
self.anyWidget = widget
def tearDown(self):
self._stdin.stop()
self._select.stop()
self._psutil.stop()
self.popen.cleanup()
mocks.teardown_test(self)
def test_format(self):
self.psutil.cpu_percent.return_value = 21.0