You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2017/06/09 14:37:18 UTC
[jira] [Commented] (SLING-6949) Create testing utilities for
email-enabled applications
[ https://issues.apache.org/jira/browse/SLING-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044505#comment-16044505 ]
Robert Munteanu commented on SLING-6949:
----------------------------------------
Initial version commited in [r1798227|https://svn.apache.org/r1798227]
> 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
>
> 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.3.15#6346)