Comment 6 for bug 770428

On Tue, May 10, 2011 at 10:59 AM, Robert Marianski <
<email address hidden>> wrote:

> I was assuming these tracer emails would just be blog post entries, and
> then the test would be to verify that unique text, like a uuid or
> timestamp, was present on the page.
>
> What are the negative consequences of just sending an email to a
> separate private community? If we want to eliminate the content feeds
> side effect, we can create a separate dummy user just for this tracer
> private community.
>
> I guess this makes the test to verify that the mail went through more
> complicated, but it might be easier to move the complexity there than to
> build something separate in karl.
>
>
Well, actually, now that I remember, what we had actually discussed is a
specialized blog tool in a specialized community. So, actually, all of the
mailin machinery would be exercised but you wouldn't end up with an enormous
number of blog entries stored unnecessarily in your database. If we're
sending a tracer email every 5 minutes, that's 288 blog posts a day. After
just a week, your test community has 2016 blog posts in it, and growing.
 That just doesn't seem sustainable.

So the idea was to just create an object that looks for all the world like a
blog for the mailin tool to write a blog entry to, but instead of storing
each blog entry it would simply not the time it had last received a blog
entry. So you still have a bunch of transactions, but at least not a ton of
data you're trying to store unnecessarily. Zagy's idea also eliminates the
unnecessary transactions, but by using this dummy blog tool, we still
exercise all of the mailin machinery end to end.

Chris