We're using zope.sendmail to send mail from our applications. These 
applications are built on top of a more generic application library. It 
is this application library that depends on zope.sendmail. This 
application library listens for certain events and then can decide to 
send out an email.

Obviously, when running the tests for the concrete application no mail 
is allowed to be actually sent.

Zope.sendmail explains in its README.txt that the developer using 
zope.sendmail should himself take care of not sending emails (by setting 
up a test layer for example, that would register a no-op IMailDelivery 

I had hoped that somehow zope.sendmail would automagically "detect" it 
is used during test runs and then would not send out any mails.

I dug around in zope.testing and found the cleanup module that seems to 
provide (if I understand correctly) a global registry of things to 
cleanup after tests. I wonder if this could be extended to also be able 
to register routines for globally setting up stuff - in this case it 
could stub the mail delivery so that never ever any mail is actually 
send out when running tests.


1) how do others make sure that applications that directly or indirectly 
trigger sending mails do not actually send during testing?

2) am I on the right track thinking a "set up" equivalent of 
zope.testing.cleanup could be useful for these cases?

kind regards,

Jan-Wijbrand Kolman

Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to