I will choose another alternative which is to exclude the if __name__ == ‘__main__’ from the coverage report , of course you can do that only if you already have a test case for your main() function in your tests. As for why I choose to exclude rather than writing a new test case for … Read more
You should almost always prefer not to mock parts of the thing you’re supposed to be testing, in this case UserService. To illustrate why, consider these two tests: Provides a test double implementation for findByEmail on the repo object: it(“throws an error if the user already exists”, async () => { const email = “[email protected]”; … Read more
There are several disadvantages to the when/thenReturn, when/thenThrow and when/then syntaxes. For example, In the case of when/thenReturn, if the return type is a generic with a wildcard, and you wish to return a mock of the same type, you will be unable to avoid a compile warning. You can’t use when/thenThrow and when/then for … Read more
TLDR: Two or more distinct instances of your mock exist. Your test is using one instance and your class under test is using another instance. Or you are not using mocks at all in your class because you new up objects inside the class. Problem Overview (Classes vs Instances) Mocks are instances (that’s why they … Read more
I know that there is already an accepted answer but there is simpler solution for that problem – mocking the print in python 2.x. Answer is in the mock library tutorial: http://www.voidspace.org.uk/python/mock/patch.html and it is: >>> from StringIO import StringIO >>> def foo(): … print ‘Something’ … >>> @patch(‘sys.stdout’, new_callable=StringIO) … def test(mock_stdout): … foo() … Read more
I’ve only used one, but I’ve had good results with Michael Foord’s Mock: http://www.voidspace.org.uk/python/mock/. Michael’s introduction says it better than I could: There are already several Python mocking libraries available, so why another one? Most mocking libraries follow the ‘record -> replay’ pattern of mocking. I prefer the ‘action -> assertion’ pattern, which is more … Read more
Botocore has a client stubber you can use for just this purpose: docs. Here’s an example of putting an error in: import boto3 from botocore.stub import Stubber client = boto3.client(‘s3’) stubber = Stubber(client) stubber.add_client_error(‘upload_part_copy’) stubber.activate() # Will raise a ClientError client.upload_part_copy() Here’s an example of putting a normal response in. Additionally, the stubber can now … Read more
Webforms is notoriously untestable for this exact reason – a lot of code can rely on static classes in the asp.net pipeline. In order to test this with Moq, you need to refactor your GetSecurityContextUserName() method to use dependency injection with an HttpContextBase object. HttpContextWrapper resides in System.Web.Abstractions, which ships with .Net 3.5. It is … Read more
You need to monkeypatch datetime.now function. In example below, I’m creating fixture which I can re-use later in other tests: import datetime import pytest FAKE_TIME = datetime.datetime(2020, 12, 25, 17, 5, 55) @pytest.fixture def patch_datetime_now(monkeypatch): class mydatetime: @classmethod def now(cls): return FAKE_TIME monkeypatch.setattr(datetime, ‘datetime’, mydatetime) def test_patch_datetime(patch_datetime_now): assert datetime.datetime.now() == FAKE_TIME
Create a test rule: import ch.qos.logback.classic.Logger; import ch.qos.logback.classic.spi.ILoggingEvent; import ch.qos.logback.core.read.ListAppender; import org.junit.rules.TestRule; import org.junit.runner.Description; import org.junit.runners.model.Statement; import org.slf4j.LoggerFactory; import java.util.List; import java.util.stream.Collectors; public class LoggerRule implements TestRule { private final ListAppender<ILoggingEvent> listAppender = new ListAppender<>(); private final Logger logger = (Logger) LoggerFactory.getLogger(Logger.ROOT_LOGGER_NAME); @Override public Statement apply(Statement base, Description description) { return new Statement() { @Override … Read more