blocks|key|874134|text|根据mock+documentation的说法|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|874135|874136|补丁可以用作TestCase类装饰器。它通过装饰类中的每个测试方法来工作。当您的测试方法共享一个公共补丁集时，这可以减少样板代码。|blockquote|874137|874138|874139|这基本上意味着您可以创建一个应用了@patch装饰器的基本测试类，它将模拟您的外部调用，而内部的每个测试方法都将被执行。|874140|此外，您还可以分别在setUp()和tearDown()方法中使用start()+and+stop()补丁程序的方法：|874141|class+BaseTestCase(TestCase):
++++def+setUp(self):
++++++++self.patcher+=+patch('mymodule.foo')
++++++++self.mock_foo+=+self.patcher.start()

++++def+tearDown(self):
++++++++self.patcher.stop()|code-block|syntax|javascript|874142|entityMap|0|LINK|mutability|MUTABLE|url|http://www.voidspace.org.uk/python/mock/patch.html#mock.patch|1|https://docs.python.org/3/library/unittest.mock.html#patch-methods-start-and-stop^0|2|4|2|I|0|0|0|0|0|0|H|6|0|A|7|I|A|X|7|19|6|X|I|1|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|1B|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1E|8|@$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1H|8|@$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]]|D|@$9|1Q|A|1R|1|1S]]|E|$]]|$1|P|3|Q|5|R|7|1T|8|@]|D|@]|E|$S|T]]|$1|U|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]]]

According to the <a href="http://www.voidspace.org.uk/python/mock/patch.html#mock.patch" rel="nofollow noreferrer"><code>mock</code> documentation</a>:
<blockquote>
Patch can be used as a TestCase class decorator. It works by
decorating each test method in the class. This reduces the boilerplate
code when your test methods share a common patchings set.
</blockquote>
This basically means that you can create a base test class with <code>@patch</code> decorator applied on it that would mock your external calls while every test method inside would be executed.
Also, you can use <a href="https://docs.python.org/3/library/unittest.mock.html#patch-methods-start-and-stop" rel="nofollow noreferrer"><code>start()</code> and <code>stop()</code></a> patcher's methods in <code>setUp()</code> and <code>tearDown()</code> methods respectively:
<pre><code>class BaseTestCase(TestCase):
 def setUp(self):
 self.patcher = patch('mymodule.foo')
 self.mock_foo = self.patcher.start()

 def tearDown(self):
 self.patcher.stop()
</code></pre>

blocks|key|874163|text|添加到alecxe's+answer中，如果您使用的是teardown()，那么according+to+the+docs|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|874164|874165|您必须通过调用stop来确保修补已“撤消”。这可能比您想象的要麻烦，因为如果在setUp中引发异常，则不会调用tearDown。|blockquote|874166|874167|874168|如果在您的测试中引发异常，您的补丁将无法撤消。更好的方法是在setUp()中调用addCleanup()。然后，您可以完全省略tearDown()方法。|874169|class+BaseTestCase(TestCase):
++++def+setUp(self):
++++++++self.patcher+=+patch('mymodule.foo')
++++++++self.mock_foo+=+self.patcher.start()
++++++++self.addCleanup(self.patcher.stop)+#+add+this+line|code-block|syntax|javascript|874170|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/25857701/3357935|1|https://docs.python.org/3/library/unittest.mock.html#patch-methods-start-and-stop|2|https://docs.python.org/3/library/unittest.html#unittest.TestCase.addCleanup^0|R|A|3|F|0|14|L|1|0|0|7|4|13|5|1J|8|0|0|0|U|7|14|C|1R|A|14|C|2|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]|$9|1A|A|1B|1|1C]]|E|$]]|$1|F|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1N|8|@$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]]|D|@$9|1U|A|1V|1|1W]]|E|$]]|$1|N|3|O|5|P|7|1X|8|@]|D|@]|E|$Q|R]]|$1|S|3|-4|5|6|7|1Y|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]|10|$5|V|W|X|E|$Y|11]]|12|$5|V|W|X|E|$Y|13]]]]

Just to add to <a href="https://stackoverflow.com/a/25857701/3357935">alecxe's answer</a>, if you are using <code>teardown()</code> then <a href="https://docs.python.org/3/library/unittest.mock.html#patch-methods-start-and-stop" rel="noreferrer">according to the docs</a> 

<blockquote>
 you must ensure that the patching is “undone” by calling <code>stop</code>. This can be fiddlier than you might think, because if an exception is raised in the <code>setUp</code> then <code>tearDown</code> is not called.
</blockquote>

If an exception is raised in your tests, your patching won't be undone. A better way would be to call <a href="https://docs.python.org/3/library/unittest.html#unittest.TestCase.addCleanup" rel="noreferrer"><code>addCleanup()</code></a> inside your <code>setUp()</code>. Then you can omit the <code>tearDown()</code> method altogether.

<pre><code>class BaseTestCase(TestCase):
 def setUp(self):
 self.patcher = patch('mymodule.foo')
 self.mock_foo = self.patcher.start()
 self.addCleanup(self.patcher.stop) # add this line
</code></pre>

blocks|key|5450937|text|我最终创建了一个测试跑步器来服务于我的目的。我需要模拟文件存储，以便在测试时映像不会实际写入文件系统。在许多测试中都调用了图像对象，因此修补每个类都不是DRY。此外，我注意到模拟文件本身会将其留在系统中，以防测试失败。但是这个方法没有。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5450938|我在项目根目录中创建了一个文件runner.py|5450939|#+runner.py
from+unittest.mock+import+patch

from+django.test.runner+import+DiscoverRunner

from+myapp.factories+import+ImageFactory


class+UnitTestRunner(DiscoverRunner):

++++@patch('django.core.files.storage.FileSystemStorage.save')
++++def+run_tests(self,+test_labels,+mock_save,+extra_tests=None,+**kwargs):
++++++++mock_save.return_value+=+ImageFactory.get_image()
++++++++return+super().run_tests(test_labels,+extra_tests=None,+**kwargs)|code-block|syntax|javascript|5450940|然后我将使用python+manage.py+tests+--testrunner=runner.UnitTestRunner运行我的测试|5450941|5450942|为了清楚起见，ImageFactory.get_image方法是一个自定义方法|5450943|from+django.core.files.base+import+ContentFile
from+factory.django+import+DjangoModelFactory
from+io+import+BytesIO
from+PIL+import+Image+as+PilImage
from+random+import+randint

class+ImageFactory(DjangoModelFactory):

++++@classmethod
++++def+get_image(cls,+name='trial',+extension='png',+size=None):
++++++++if+size+is+None:
++++++++++++width+=+randint(20,+1000)
++++++++++++height+=+randint(20,+1000)
++++++++++++size+=+(width,+height)

++++++++color+=+(256,+0,+0)

++++++++file_obj+=+BytesIO()
++++++++image+=+PilImage.new("RGBA",+size=size,+color=color)
++++++++image.save(file_obj,+extension)
++++++++file_obj.seek(0)
++++++++return+ContentFile(file_obj.read(),+f'{name}.{extension}')|5450944|entityMap^0|24|3|0|F|9|0|0|6|1L|0|0|7|M|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|11|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|15|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|R|3|S|5|J|7|19|8|@]|D|@]|E|$K|L]]|$1|T|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|U|$]]

I ended up creating a test runner to serve my purpose. I needed to mock the file storage so that images do not actually write to the file system while testing. The images object is being called in many tests thus patching each class would not be <code>DRY</code>. Also, I noticed that mocking the file itself would leave it on the system in case the test failed. But this method didn't.

I created a file <code>runner.py</code> in the project root

<pre class="lang-py prettyprint-override"><code># runner.py
from unittest.mock import patch

from django.test.runner import DiscoverRunner

from myapp.factories import ImageFactory


class UnitTestRunner(DiscoverRunner):

 @patch('django.core.files.storage.FileSystemStorage.save')
 def run_tests(self, test_labels, mock_save, extra_tests=None, **kwargs):
 mock_save.return_value = ImageFactory.get_image()
 return super().run_tests(test_labels, extra_tests=None, **kwargs)
</code></pre>

Then I would run my tests using <code>python manage.py tests --testrunner=runner.UnitTestRunner</code>

<hr>

Just for clarity the <code>ImageFactory.get_image</code> method is a custom method

<pre class="lang-py prettyprint-override"><code>from django.core.files.base import ContentFile
from factory.django import DjangoModelFactory
from io import BytesIO
from PIL import Image as PilImage
from random import randint

class ImageFactory(DjangoModelFactory):

 @classmethod
 def get_image(cls, name='trial', extension='png', size=None):
 if size is None:
 width = randint(20, 1000)
 height = randint(20, 1000)
 size = (width, height)

 color = (256, 0, 0)

 file_obj = BytesIO()
 image = PilImage.new("RGBA", size=size, color=color)
 image.save(file_obj, extension)
 file_obj.seek(0)
 return ContentFile(file_obj.read(), f'{name}.{extension}')
</code></pre>

I need to create some kind of <code>MockMixin</code> for my tests. It should include mocks for everything that calls external sources.
For example, each time I save model in admin panel I call some remote URLs. It would be good, to have that mocked and use like that:

<pre><code>class ExampleTestCase(MockedTestCase):
 # tests
</code></pre>

So each time I save model in admin, for example in functional tests, this mock is applied instead of calling remote URLs.

Is that actually possible? I'm able to do that for 1 particular test, that is not a problem. But it'd be more useful to have some global mock because I use it a lot.

Django tests - patch object in all tests

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我需要为我的测试创建某种类型的MockMixin。它应该包含对调用外部源的所有内容的模拟。例如，每次我在管理面板中保存模型时，我都会调用一些远程URL。这将是很好的，有这样的嘲笑和使用：class ExampleTestCase(MockedTestCase):    # tests因此，每次我在admin中保存模型时...

问Django测试-所有测试中的补丁对象
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django测试-所有测试中的补丁对象EN