Stefano Bagnara wrote:
Bernd Fondermann wrote:
Hi,
I uploaded the current code into JIRA JAMES-442
(http://issues.apache.org/jira/browse/JAMES-442)
I looked around in the code when you uploaded them: I saw you left the
old source folder, too (that should be removed, it is confusing).
ooops! yeah, should have been removed.
+ feature: add option to make the load adaptive, so that we can
get to the limits of James
+1 My preferred feature ;-) I would like to use it to test optimizations
and be sure we don't introduce bottlenecks with changes.
how do we implement that? there is more than one wheel which can be tuned.
a canonical first solution would be to constantly increase the number of
mails sent.
+ feature: do more functional testing, not just pure end-to-end
tests, by parsing the received mail and check if, for example, a
footer had been added.
Maybe this is much more a functional test that could be added to the
default unit tests.
agreed, all which can be covered by unit tests should be covered there.
what I am proposing here is a feature to test more complex mail flows.
+ integration: look into JMeter integration
Yes, maybe this could help creating custom scenario, and maybe the best
feature would be an SMTP proxy to log an SMTP session and add it as a
template of the load test (JMeter do that for the HTTP tests).
I see. would not be my top priority.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
