36

I am a pythoner. At these days I am driving myself to do a more complete unit test on some core module in my project. Since we always do unit test with methods 'assertEqual', 'assertTrue' and so on, these methods all require a return value from the function being tested, I am wondering how to do a plain unit test on some function without a return value.

I would like to show a tiny example here, how to test function def foo(self, msg) in HelloTest?

class HelloTest(object):
    def foo(self, msg):
        MSG = msg.upper()
        self.bar(MSG)

    def bar(self, MSG):
        print MSG
Yarkee
  • 8,494
  • 5
  • 27
  • 27

6 Answers6

17

As another answer mentioned, you can use the Python mock library to make assertions about calls to functions/methods

from mock import patch
from my_module import HelloTest
import unittest

class TestFoo(unittest.TestCase):

    @patch('hello.HelloTest.bar')
    def test_foo_case(self, mock_bar):

        ht = HelloTest()

        ht.foo("some string")
        self.assertTrue(mock_bar.called)
        self.assertEqual(mock_bar.call_args[0][0], "SOME STRING")

This patches out the bar method on HelloTest and replaces it with a mock object that records calls against it.

Mocking is a bit of a rabbit hole. Only do it when you absolutely have to because it does make your tests brittle. You'll never notice an API change for a mocked object for instance.

aychedee
  • 23,571
  • 7
  • 75
  • 82
  • in line `self.assertEqual(ob.msg, "SOME STRING")`, where is ob coming from? – Isaac Sekamatte May 24 '19 at 06:04
  • 3
    You know... I really don't know? Looks like I made a mistake a 6 years ago :-) It should be something like: `self.assertEqual(mock_bar.call_args[0][0], "SOME STRING")` I'll update the answer. – aychedee May 24 '19 at 15:07
13

I don't quite understand why everybody wants to check that foo calls bar.

Foo has some functionality and this functionality needs to be tested. If foo is using bar to do this should not be of my concern.

The desired result is that after foo(msg) is called, is that msg.upper() is sent to stdout.

You can redirect stdout to a string buffer and check if the content of this string buffer matches what you expect.

Example:

import sys
import unittest
from io import TextIOWrapper, BytesIO

class TestScript(unittest.TestCase):
    def setUp(self):
        self._old_stdout = sys.stdout
        sys.stdout = TextIOWrapper(BytesIO(), sys.stdout.encoding)

    def _output(self):
        self._stdout.seek(0)
        return self._stdout.read()

    def test_foo(self):
        hello_test = HelloTest()
        hello_test.foo("blub")
        self.assertEqual(self._output(), "BLUB")

    def tearDown(self):
        sys.stdout = self._old_stdout
        self._stdout.close()

You can also do that for stdin (and write to stdin to mock some input) and you can subclass TestIOWrapper if you need anything special to be done, like allowing non-unicode text to be sent to sys.stdout without using sys.stdout.buffer (Python 2 vs. Python 3). There is an example for that in this SO answer. When you (still) use Python 2 only, then using StringIO might be better than using the io module.

Community
  • 1
  • 1
JonnyJD
  • 2,463
  • 1
  • 28
  • 43
10

In this particular case, I would mock print, then then use the mock in my assertion.

In Python, you will use the Mock package to mock.

Jordan Dea-Mattson
  • 5,753
  • 5
  • 37
  • 53
  • 2
    Well, if he is using anything below Python 3 then it's not that simple to mock print. He could mock sys.stdout, but he would have to change bar – aychedee Apr 11 '13 at 08:12
  • 1
    This answer would work if the question was how to test `bar`, but not if we are testing `foo`, since `foo` doesn't call `print`. The functionality of `foo` is to call `bar` with a capitalised message. The answer from @aychedee is correct since it only tests the functionality of `foo`, not `bar`. – bgordon Sep 10 '19 at 16:31
8

Thanks to @Jordan 's introduction, I code this and think it is a workable unit test for HelloTest.foo

from mock import Mock
import unittest


class HelloTestTestCase(unittest.TestCase):
    def setUp(self):
        self.hello_test = HelloTest()

    def tearDown(self):
        pass

    def test_foo(self):
        msg = 'hello'
        expected_bar_arg = 'HELLO'
        self.hello_test.bar = Mock()

        self.hello_test.foo(msg)
        self.hello_test.bar.assert_called_once_with(expected_bar_arg)


if __name__ == '__main__':
    unittest.main()
Yarkee
  • 8,494
  • 5
  • 27
  • 27
5

your code can be as given below which does same task as above:

class HelloTest(object):

    def foo(self, msg):
        self.msg = msg.upper()
        self.bar()

    def bar(self):
        print self.msg

Unit test is :

from hello import HelloTest
import unittest

class TestFoo(unittest.TestCase):
    def test_foo_case(self):
        msg = "test"
        ob = HelloTest()
        ob.foo(msg)
        expected = "TEST"
        self.assertEqual(ob.msg, expected)

if __name__ == '__main__':
    unittest.main(exit=False)
Zangetsu
  • 1,660
  • 16
  • 25
3

In Python 3, you can tell print where to print to:

print(*objects, sep=' ', end='\n', file=sys.stdout, flush=False)

So add an optional argument:

def bar(self, MSG, file=sys.stdout):
    print(MSG, file=file)

In normal usage, it will print to stdout, but for unit tests you can pass your own file.

In Python 2 it's a bit messier, but you can redirect stdout to a StringIO buffer:

import StringIO
import sys

out = StringIO.StringIO()
sys.stdout = out

# run unit tests

sys.stdout = sys.__stdout__

# check the contents of `out`
Community
  • 1
  • 1
Brendan Long
  • 51,248
  • 19
  • 139
  • 179
  • 1
    Good solution for doing unit test on function with output. But what I care most is how to test `def foo(self, msg)`, since not all function do something with stdout – Yarkee Apr 11 '13 at 04:06