blocks|key|1640576|text|我将对电子邮件服务器执行mock操作，并配置该模拟对象以适当地接受/拒绝电子邮件(取决于您的测试)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1640577|要有效地做到这一点，您需要一个接口来与您的电子邮件服务器进行对话。为了进行测试，实现是一个模拟对象。对于部署，您可以将其替换为直接与邮件服务器对话的实现。|1640578|有关C%2B%2B模拟框架，请参阅此SO+question。|1640579|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Mock_object|1|https://stackoverflow.com/questions/38493/are-there-any-good-c-mock-object-frameworks^0|C|4|0|0|0|E|B|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

I would <a href="http://en.wikipedia.org/wiki/Mock_object" rel="nofollow noreferrer">mock</a> the email server, and configure that mocked object to accept/reject emails as appropriate (depending on your tests).

To do this effectively, you need an interface to talk to your email server through. For testing, the implementation is a mocked object. For deployment you substitute this with an implementation that talks directly to a mail server.

See this <a href="https://stackoverflow.com/questions/38493/are-there-any-good-c-mock-object-frameworks">SO question</a> for C++ mocking frameworks.

blocks|key|382905|text|由于您很可能不想测试套接字的使用情况，因此可以考虑用不涉及任何TCP通信的虚拟服务器实现替换代码的这一部分。只需对来自客户端的预期请求进行硬编码，并让您的虚拟服务器做出适当的响应。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|382906|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As you most likely don't want to test you use of sockets, you might think about replacing that part of your code with a dummy server implementation that doesn't involve any TCP communication. Just hardcode the expected requests from your client and let your dummy server respond appropriately.

blocks|key|234114|text|你只需要找到一种方法来用存根替换真正的东西，这完全在你的控制之下。通常，这是通过Rhino.Mocks等模拟框架来完成的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|234115|顺便说一句，如果你使用一个“真正的”电子邮件帐户，那么它就不再是一个单元测试，而是一个集成测试……|234116|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ayende.com/projects/rhino-mocks.aspx^0|14|B|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You just have to find a way to replace the real thing with a stub, that is fully under your control. Usually, this is done with mocking frameworks like <a href="http://www.ayende.com/projects/rhino-mocks.aspx" rel="nofollow noreferrer">Rhino.Mocks</a>.

Btw.: If you'd use a 'real' email account, then it's not a unit test anymore, but an integration test...

blocks|key|1640710|text|我将假设通过测试后端，您指的是实际与电子邮件服务器对话的代码，并且为了测试您的软件的其余部分，您有mocked这一层。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1640711|现在，这可能是也可能不是集成测试，这取决于您的定义单元。坦率地说，我并不关心您决定如何命名它，但是如果您编写了一些运行迅速且经常执行的自动化测试，那么它们也可以使用与您的单元测试相同的平台。|1640712|我尝试这样写，这样它至少可以通过以下两种方式工作-第一种方式是连接到进程本地电子邮件服务器，您可以根据需要设置和配置该服务器。在Java语言中，我使用的是Dumpster，但我相信C%2B%2B也有类似的东西。第二种方法是连接到至少一个您可以编写脚本的本地电子邮件服务器。一个你可以随心所欲的飞溅(所以不是真实的或在开发人员之间共享的)，并对其运行相同的测试集。原因是SMTP服务器的开发人员讨厌每个人，您将希望检查您的存根是否像真实的一样工作。我认为这等同于One+Database+Per+Developer。|1640713|现在，如果您还没有编写自己的SMTP客户端，而只是在现有的第三方API周围有一个facade，那么我就不太可能在假设第三方API已经受到足够的打击以至于bug已经掉出来的情况下进行“集成测试”。我会考虑模仿第三方API并验证外观是否如预期的那样工作。|1640714|1)也许你可以在CI周期中做到这一点，然后在所有开发人员之间共享一组电子邮件服务器，本地运行只需使用类似的C%2B%2B垃圾箱。|1640715|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Mock_object|1|http://quintanasoft.com/dumbster/|2|http://dbunit.wikidot.com/onedatabaseperdeveloper|3|http://en.wikipedia.org/wiki/Facade_pattern^0|1D|6|0|0|0|25|8|1|6A|Q|2|0|14|6|3|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]|$A|18|B|19|1|1A]]|C|$]]|$1|H|3|I|5|6|7|1B|8|@]|9|@$A|1C|B|1D|1|1E]]|C|$]]|$1|J|3|K|5|6|7|1F|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1G|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]|V|$5|O|P|Q|C|$R|W]]|X|$5|O|P|Q|C|$R|Y]]]]

I'm going to assume by testing the back end you are referring to the bit of code that actually talks to the Email server and to test the rest of your software you have <a href="http://en.wikipedia.org/wiki/Mock_object" rel="nofollow noreferrer">mocked</a> this layer.

Now this may or may not be integration tests depending on your definition unit. Frankly I don't care what you decide to call it but if you write some automated tests that are quick to run and are executed often then they might as well use the same platform as your unit tests.

I'd try to write this so it can work in at lest the following two ways - The first would be that it connects to an process-local email server that you can set up and configure as you need. In Java I use <a href="http://quintanasoft.com/dumbster/" rel="nofollow noreferrer">Dumpster</a> but I'm sure alikes exist for C++. 
The second would be to connect to at least one local email server that you can script. One that you can splatter as much as you like (so NOT real or shared between developers¹) and run the same set of tests against that. The reason being that the developers of SMTP servers hate everyone and you will want to check that your stub works the same as a real thing. This I see as the equivalent to <a href="http://dbunit.wikidot.com/onedatabaseperdeveloper" rel="nofollow noreferrer">One Database Per Developer</a>.

Now if you have not written your own SMTP client and just have a <a href="http://en.wikipedia.org/wiki/Facade_pattern" rel="nofollow noreferrer">facade</a> around an existing 3rd party API I less likely to "integration test" this on the assumption that the 3rd party API has been battered enough that bugs have already fallen out. I would look at mocking the 3rd party API and validating that the facade works as expected.

1) Maybe you could do this just during the CI cycle, so then share one set of email servers between all developers and the local run just uses a C++ Dumpster alike.

blocks|key|383664|text|Andrew关于模仿邮件API的看法是正确的。您在C中遇到的问题可以通过以下两种方式之一来解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|383665|383666|提供了一个可以模拟的简单C%2B%2B包装器。|unordered-list-item|383667|使用链接器来提供C+api的测试/模拟版本，您必须使用与库提供的头文件相同的头文件，但您的单元测试链接到模拟C函数而不是库。|383668|383669|有一本很好的书解决了如何在困难的情况下进行单元测试："Working+Effectively+with+Legacy+Code"，我非常推荐这本书。不要被书名吓跑了，本书将遗留代码视为任何没有单元测试的代码。|383670|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

Andrew is correct about Mocking the mail API. Your problem with this being in C can be addressed in one of two ways.

<ul>
<li>provide a simple C++ wrapper that can be mocked.</li>
<li>Use the linker to provide your test/mock version of the C api, you must use the same header files as the library provides but your unit tests link with your mock C functions instead of the library.</li>
</ul>

There is a great book that addresses how to unit test in difficult situations: "Working Effectively with Legacy Code", I cannot recommend this book highly enough. Don't be put off by the title, the book regards legacy code as any code without unit tests.

I'm working on a desktop email client right now, and I want to unit test my backend. However, I can't see a way to make that work. In order for my code to work, it has to connect to a working mail server. Unless I tie my unit tests to an email account, and make sure that account matches the state my tests expect, I don't see how I can manage this.

Does anyone have any ideas on how to test this sort of application, where it relies on external factors by design?

EDIT:

To add some details: I'm working on a C++ higher level mail client library for my application, which uses libEtPan, a C library, to actually handle the details of connecting to the mail server and interacting with it.

How to unit test an email client

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我现在正在开发一个桌面电子邮件客户端，我想对我的后端进行单元测试。然而，我看不到有什么方法可以做到这一点。为了让我的代码正常工作，它必须连接到一个正常工作的邮件服务器。除非我将我的单元测试绑定到一个电子邮件帐户，并确保该帐户与我的测试期望的状态相匹配，否则我不知道如何管理它。有没有人对如何测试这种依赖于外部因素的应用程...

问如何对电子邮件客户端进行单元测试
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何对电子邮件客户端进行单元测试EN