Stefano Bagnara wrote:
It would be cool to have a performance/stress test that allow to test
common setups. A benchmark could measure memory used and time needed to
perform a given task.
yes, that would be excellent!
such tests could also be 'health tests' to 'certify' an intermediate or
rele
Not bad either ... :-)
Siegfried Goeschl
Stefano Bagnara wrote:
Siegfried Goeschl wrote:
Hi Stefano,
maybe I can provide a few tips and tricks to improve testing
Thank you for the tips!
+) Jakarta CommonsEmail uses Dumbster to test SMTP sending and testing
the result - see http://sourc
Siegfried Goeschl wrote:
> Hi Stefano,
>
> maybe I can provide a few tips and tricks to improve testing
Thank you for the tips!
> +) Jakarta CommonsEmail uses Dumbster to test SMTP sending and testing
> the result - see http://sourceforge.net/projects/dumbster and
> http://quintanasoft.com/dumbs
Hi Stefano,
maybe I can provide a few tips and tricks to improve testing
+) Jakarta CommonsEmail uses Dumbster to test SMTP sending and testing
the result - see http://sourceforge.net/projects/dumbster and
http://quintanasoft.com/dumbster/
+) for the YAAFI Avalon Container I use various inte
> a specific class from this set was named "POP3Hammering" to reproduce a
> certain "stuck file" issue under windows. is this still relevant?
I think I've found this issue again while hammering my james trunk using
file repositories. file repositories locking has something wrong.
> from the way h
hi,
some more unit tests have been added to JAMES-427.
as suggested, i looked into the pre-v2and3-merger-trunk tag. the tests
contained in there were run in a stand-alone app against a full-fledged
James instance. what we have now is a much more lightweight approach
with very short turn-aroun
