Thanks Alfred

I've been trying to figure out how to get better quality assurance -
it starts to become almost impossible with some sort of tool to help,
once a program gets a bit big - and Dada got that way years ago

As a life-saver, I've been using the Test'ing CPAN modules, which are
a god-send Currently, every-time I make a new distribution, tests on
the code are performed At the moment there are almost 400 tests
done Here's what gets outputted:

 Justins-Computer:/Library/WebServer/CGI-Executables/dada justin$  

prove -r t/1_use_modules ok 1/83 skipped: GD not installed t/1first ok t/DADA_Mail_MailOut ok 1/0# set it is: t/DADA_Mail_MailOut ok t/DADA_MailingList_Settings ok t/new_list ok t/podtest ok t/Template_template NOK 139 # Failed test 'sending_options_screen tmpl' # in t/Template_template t at line 109 # Errors: sending_options_screen tmpl # (85:3) with no opening # (103:2) with no opening # Looks like you failed 1 test of 164 t/Template_template dubious Test returned status 1 (wstat 256, 0x100) DIED FAILED test 139 Failed 1/164 tests, 99 39% okay Failed Test Stat Wstat Total Fail List of Failed

------------------------------------------------------------------------

 t/Template_template
t    1   256   164    1  139
 1 subtest skipped

 Failed 1/7 test scripts
 1/392 subtests failed

 Files=7, Tests=392,  7 wallclock secs ( 5
03 cusr +  0
77 csys  

= 5 80 CPU) Failed 1/7 test programs 1/392 subtests failed

So at the moment, only one test is failing - and it's actually a bug
in the testing suite Go figure

If you want to see what the tests look like, they're at:

http://mojomail
cvs
sourceforge
net/mojomail/dada_mail_stable/dada/t

They're pretty simple to write, so hopefully, I'll write more ;) The
new auto-reload mailout feature is pretty heavily tested, so all the
changes I make to it every week get looked at carefully and
automatically and I'm sure I don't break anything It's nice

Cheers,