[
https://issues.apache.org/jira/browse/SLING-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-6949.
------------------------------------
Resolution: Fixed
Fix Version/s: Testing Email 1.0.0
Added extra logging in [r1798597|https://svn.apache.org/r1798597]
> Create testing utilities for email-enabled applications
> -------------------------------------------------------
>
> Key: SLING-6949
> URL: https://issues.apache.org/jira/browse/SLING-6949
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Testing Email 1.0.0
>
>
> When working with email-enabled applications it is sometimes desirable to
> interact with the emails send by the applications, either by verifying the
> contents of the emails or just validating that a certain email is sent.
> A good solution for this is
> [Wiser|https://github.com/voodoodyne/subethasmtp/blob/master/Wiser.md], which
> works quite well.
> One scenario where this does not apply is when the application under test is
> running as a container, and it cannot access the host application to deliver
> emails to the Wiser instance.
> To have an unitary approach I propose that we create an OSGi bundle which
> wraps Wiser and starts in the Sling application. The messages received by
> Wiser can then be read using an HTTP API.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
