Hi,
Looks like development of QPSMTP has a tendancy to break little things,
and I think they will be more and more as code, users and usage
scenarios get added.
The t/ directory for QP seems a bit abandoned, and doesn't seem very
inviting to write tests. Is there any documentation on how tests whould
be written for QP and it's plugins?
Looking at the existing tests, it seems that they are very focused on
testing one component at a time. I think that a test framework should be
written (I'm volunteering to write it) for QP. I think it should be
oriented to starting the server with a configuration specified in the
test (so plugins could be activated and deactivated per test), and then
having an SMTP conversation with the server (look at Test::SMTP),
proving that the plugins work. What I don't have clear is how to do this
cleanly (any ideas on how a test should look like?), how to start QP in
it's different server variants (fork, prefork, threaded, etc)?.
I think the idea is having a big base of tests for core functionality
and giving plugin developers the chance to test their plugin, and how
that plugin works with other plugins easily, maybe with the posibility
to insert their plugin (easily) to existing tests to see if it breaks
anything unexpectedly.
Please give me some feedback on what you think the testing framework
should have, how it should look like, ideas, etc. and let's see if I can
cook something up that fits the core developers and the plugin
developers point of view.
Jose Luis Martinez
[EMAIL PROTECTED]
