In doing a bit of digging, it seems that as long as deeper modules remain importable, they’ll be discovered via python -m unittest discover. The solution, then, was simply to add a __init__.py file to each directory to make them packages. . ├── LICENSE ├── models │ └── __init__.py ├── README.md ├── requirements.txt ├── tc.py … Read more
You can use self._testMethodName. This is inherited from the unittest.TestCase parent class. def setUp(): print(“In method”, self._testMethodName)
Add –source=. to the coverage run line. It will both limit the focus to the current directory, and will search for .py files that weren’t run at all.
In my experience, image comparison tests end up bring more trouble than they are worth. This is especially the case if you want to run continuous integration across multiple systems (like TravisCI) that may have slightly different fonts or available drawing backends. It can be a lot of work to keep the tests passing even … Read more
Having the teardown logic in __del__ can make your program incorrect or harder to reason about, because there is no guarantee on when that method will get called, potentially leading to the warning you got. There are a couple of ways to address this: 1) Expose a method to close the session, and call it … Read more
I think that many of the difficulties here are wrapped up in the treatment of the “call” object. It can be thought of as a tuple with 2 members (args, kwargs) and so it’s frequently nice to unpack it: args, kwargs = call Once it’s unpacked, then you can make your assertions separately for args … Read more
No, autospeccing cannot mock out attributes set in the __init__ method of the original class (or in any other method). It can only mock out static attributes, everything that can be found on the class. Otherwise, the mock would have to create an instance of the class you tried to replace with a mock in … Read more
Empty lists/dicts evaluate to False, so self.assertTrue(d) gets the job done.
To run only a single specific test, you can use: python -m unittest test_module.TestClass.test_method More information is here.
I finally figured it out working on another problem. The problem was that my test couldn’t find an import. It looks like you get the above error if your test fails to import. This makes sense because the test suite can’t import a broken test. At least I think this is what is going on … Read more