python-unittest

I have a service that uses the googleads library in python, I want to unit test these functions but do not know how to go about mocking this aspect. When I used PHP and Zend Framework it was pretty easy to mock clients, as I could tell what was expected to be called, and mock what was returned, but I do not know how to do this here. Could you point to a good resource to do learn more about it? Here's some example code I'd like to test (get_account_timezone): from googleads import AdWordsClient from googleads.oauth2 import GoogleRefreshTokenClient from dateutil import tz class AdWords: ADWORDS

I need to make a call to a web API after each pyunit test in a test suite passes or fails, so I basically need access to the test status in the tearDown method. But I can't find (or I've completely missed it) any documentation on who to access this data. Any ideas? Use TestResult . import unittest class TestFoo(unittest.TestCase): def test_ok(self): self.assertEqual(1+2, 3) def test_fail(self): self.assertEqual(1+2, 4) def test_error(self): 1/0 @unittest.skip('blah') def test_skip(self): self.assertEqual(42, 42) class MyResult(unittest.TextTestResult): def addError(self, test, err): self.call

in unittest python library, exists the functions setUp and tearDown for set variables and other things pre and post tests. how I can run or ignore a test with a condition in setUp ? You can call if cond: self.skipTest('reason') in setUp() . Instead of checking in setUp , use the skipIf decorator. @unittest.skipIf(not os.path.exists("somefile.txt"), "somefile.txt is missing") def test_thing_requiring_somefile(self): ... skipIf can also be used on the class, so you can skip all contained tests if the condition does not hold. @unittest.skipIf(not os.path.exists("somefile.txt"), "somefile.txt is

I am using the command: nosetests test.py When this is run only the first line of the description gets printed. I want the whole description along with the test name. How do i do that? test.py file import unittests class TestClass(unittest.TestCase): def test_1(self): """this is a long description // continues on second line which does not get printed """ some code; self.assertTrue(True) def test_2(self): """this is another or different long description // continues on second line which does not get printed """ some code; self.assertTrue(True) if __name__ == '__main__': unittest.main()

I want to my Django tests to create and modify media files. So, much like Django tests do with databases, I want to set up an empty MEDIA_ROOT folder before each test is run. I figured I'll create a temporary folder and point MEDIA_ROOT to it. However, I can't figure out where to put the code that does this. In this example , a special Runner is created. The runner sets up the media root and tears it down. Unfortunately, setup_test_environment is called once before the first test function is run, and not every time a test is run. I tried creating a FileSystemTestCase class that sets up the

I'd like to add some custom assert methods to a TestCase. As a simple example, I've just put one inside the test class below. It works as expected, but when the output is generated the traceback includes the custom assert in the output. What is the step necessary to make it behave like assertEqual()? The code for assertEqual is in TestCase, but the actual line that raises the assertion does not appear in the traceback. What do I need to do to make test_something2's output look more like test_something1's? import unittest class TestCustomAssert(unittest.TestCase): def assertSomething(self, s):

I am currently running a unittest script which successfully passes the various specified test with a nagging ImportWarning message in the console: ...../lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__ return f(*args, **kwds) .... ---------------------------------------------------------------------- Ran 7 tests in 1.950s OK The script is run with this main function: if __name__ == '__main__': unittest.main() I have read that warnings can be surpressed when the script is called like this: python