How to unit test a mail client

Question

I am working on a desktop email client right now and I want to unit test my backend. However, I see no way to do this work. For my code to work, it must connect to a working mail server. If I do not associate my unit tests with an email account and make sure that the account matches the state that my tests expect, I don’t see how I can do this.

Does anyone have any ideas on how to test such an application where it relies on external design factors?

EDIT:

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

Answer 1

I'm going to assume, by testing the back end, you are referencing a bit of code that actually talks to the email server and tests the rest of your software that you have mocked at this layer.

. , , , , , , -.

, , . , , . Java Dumpster, , ++ . - , , , script. , , ( ¹) . , SMTP- , , , . .

, SMTP- facade API, " ", , API , . API , , .

1) , CI, , Cump Dumpster.

Answer 2

mock / ( ).

, , . . , .

. SO - ++.

Answer 3

, . , Rhino.Mocks.

Btw: "" , unit test, ...

Answer 4

, , , , - TCP. .

Answer 5

Mocking mail API. , C, .

• ++-, .
• / C api, , , C .

There is a large book that discusses unit test problems in complex situations: “Working Effectively with Legacy Code,” I cannot recommend this book highly enough. Do not disconnect by name, the book considers obsolete code like any code without unit tests.