The behaviour is intentional, but the documentation could make this clearer. If you look at the first paragraph in the test discovery section, it says: For a project’s tests to be compatible with test discovery they must all be importable from the top level directory of the project (in other words, they must all be … Read more
Have you tried pip install coverage? The coverage plugin depends on separate coverage module, which is not a nose’s dependency, so needs to be installed manually.
Access bar using spike.bar. Imported bar is not affected by mock.patch. from unittest import TestCase import unittest from mock import patch, MagicMock from spike import T1 import spike # <—- class TestShit(TestCase): @patch(‘spike.T1.foo’, MagicMock(return_value=”patched”)) def test_foo(self): foo = T1().get_foo() self.assertEqual(‘patched’, foo) @patch(‘spike.bar’) def test_bar(self, mock_obj): mock_obj.return_value=”patched” bar = spike.bar() # <—– self.assertEqual(‘patched’, bar) if __name__ … Read more
I had the same problem and found an answer in a related question work for me. Just remove the __init__.py in the project root.
As of March 2022 this answer is updated to support Python versions between 3.4 and 3.11 (including the newest development Python version). Classification of errors / failures is the same that is used in the output unittest. It works without any modification of code before tearDown(). It correctly recognizes decorators skipIf() and expectedFailure. It is … Read more
assert expression, info For instance, >>> assert False, “Oopsie” Traceback (most recent call last): File “<stdin>”, line 1, in <module> AssertionError: Oopsie From the docs: Assert statements are a convenient way to insert debugging assertions into a program: assert_stmt ::= “assert” expression [“,” expression] The simple form, assert expression, is equivalent to if __debug__: if … Read more
The way I’ve done it is create fake responses, this way you can test the parse function offline. But you get the real situation by using real HTML. A problem with this approach is that your local HTML file may not reflect the latest state online. So if the HTML changes online you may have … Read more
If you use py27+ or py32+, the solution is pretty simple: test_suite=”tests”,
I used to use Nose because it was the default with Pylons. I didn’t like it at all. It had configuration tendrils in multiple places, virtually everything seemed to be done with an underdocumented plugin which made it all even more indirect and confusing, and because it did unittest tests by default, it regularly broke … Read more
Even better than remembering to use -s is to use the set_trace variant that comes with Nose. Add from nose.tools import set_trace; set_trace() wherever you’d like to break in to the debugger. The stdin/out redirection will be taken care of for you. The only strange side effect I’ve run into is the inability to restart … Read more