首页 > 解决方案 > 即使类被实例化,assert_call() 也会引发异常

问题描述

使用这个答案作为模型,我正在测试以下实例化类(EmailMultiAlternatives)的方法:

管理工具/emailer.py

from django.core.mail import EmailMultiAlternatives
from django.template.loader import render_to_string
from django.utils.html import strip_tags


def send_email(template_path, context, subject_line, from_email, to=[], cc=[], bcc=DEFAULT_BCC_EMAILS):
    msg_html = render_to_string(template_path, context)
    msg_plain = strip_tags(msg_html)
    email = EmailMultiAlternatives(subject_line, msg_plain, from_email, to, cc=cc, bcc=bcc)
    email.attach_alternative(msg_html, "text/html")
    email.send()

使用test.py

from unittest.mock import patch

from django.core.mail import EmailMultiAlternatives
from django.template.loader import render_to_string
from django.test import TestCase

from admintools.emailer import send_email


class EmailerTestCase(TestCase):

    @patch('django.core.mail.EmailMultiAlternatives')
    def test_send_email(self, mockEmailMultiAlternatives):
        context = {}
        template_path = "emails/closings/seller_pre_close_update_prompt.html"
        msg_plain = render_to_string(template_path, context)
        to = ['']
        cc = ['']
        send_email(template_path, {}, 'subject', "from", to, cc=cc)
        mockEmailMultiAlternatives.assert_called()

我收到AssertionError: Expected 'EmailMultiAlternatives' to have been called.即使email在测试运行期间成功创建(print(email)在实例化返回后立即通过 a 验证<django.core.mail.message.EmailMultiAlternatives object at 0x7fbf4bb4b590>)。

即使EmailMultiAlternatives正在实例化,什么可能导致断言失败?

标签: pythondjangotesting

解决方案


由于如何admintools.emailer导入EmailMultiAlternatives,您需要模拟admintools.email.EmailMultiAlternatives

@patch('admintools.emailer.EmailMultiAlternatives')
def test_send_email(self, mockEmailMultiAlternatives):

send_email通过模块全局名称调用函数,而不是通过django.core.mail属性。


推荐阅读