Per the addCleanup doc string: Cleanup items are called even if setUp fails (unlike tearDown) addCleanup can be used to register multiple functions, so you could use separate functions for each resource you wish to clean up. That would allow your code to be a bit more reusable/modular.
You have to run the test from the my-project folder, rather than from the test folder. python -m unittest test.test_file1.TestWriteDataBRToOS
You can easily capture standard output by just temporarily redirecting sys.stdout to a StringIO object, as follows: import StringIO import sys def foo(inStr): print “hi”+inStr def test_foo(): capturedOutput = StringIO.StringIO() # Create StringIO object sys.stdout = capturedOutput # and redirect stdout. foo(‘test’) # Call unchanged function. sys.stdout = sys.__stdout__ # Reset redirect. print ‘Captured’, capturedOutput.getvalue() … Read more
In my experience it is easiest if your project root is not a package, like so: project/ test.py run.py package/ __init__.py main_program.py lib/ __init__.py lib_a lib_b tests/ __init__.py test_a test_b However, as of python 3.2 , the unittest module provides the -t option, which lets you set the top level directory, so you could do … Read more
You should mock out helpers.do_it_helper: class Test_do_it(unittest.TestCase): def test_do_it(self): with patch(‘helpers.do_it_helper’) as helper_mock: helper_mock.return_value = 12 # test things Here’s an example using mock on os.getcwd(): import unittest from mock import patch def get_cwd(): from os import getcwd return getcwd() class MyTestCase(unittest.TestCase): @patch(‘os.getcwd’) def test_mocked(self, mock_function): mock_function.return_value=”test” self.assertEqual(get_cwd(), ‘test’)
The order of your patches should be reversed, as they are applied bottom up. See this comment in the python docs on nested mock arguments: Note When you nest patch decorators the mocks are passed in to the decorated function in the same order they applied (the normal python order that decorators are applied). This … Read more
Although I’m using pytest, I found the following idea in a comment. It worked really great for me, so I thought it could be useful here. Python 3: assert dict1.items() <= dict2.items() Python 2: assert dict1.viewitems() <= dict2.viewitems() It works with non-hashable items, but you can’t know exactly which item eventually fails.
As stated in the python unittest doc: The simplest TestCase subclass will simply implement a test method (i.e. a method whose name starts with test) So you will need to change your method name to something like this: def test_add_returns_zero_for_emptyString(self): self.assertEqual(Add(‘ ‘), 0)
I think what you are looking for is nose. It works like a test runner for unittest. You can drop into the debugger on errors, with the following command: nosetests –pdb
As some comments have echoed, structuring your tests in this manner is probably a design flaw in the tests themselves and you should consider restructuring them. However, if you want to do this and rely on the fact that the test runner you are using executes them in an alphabetical (seemingly) order then I suggest … Read more