On Thu, 2007-05-17 at 16:37 -0400, Matt Sergeant wrote:
> On 26-Mar-07, at 12:18 PM, Guy Hulbert wrote:
>
> > I would like to propose that we create 'config.tests' and change the
> > code in t/Test/Qpsmptd.pm from:
> > sub config_dir {
> > './config.sample';
> > }
> > to:
> > sub config_dir {
> > './config.tests';
> > }
>
> I'm thinking this might not be the best situation either... Many
> times you'll want to test a plugin in isolation...
I have some code for that. It's pretty crappy but I can post what I
have. I have a working (in production :-) auth_dbi plugin which can
do everything auth_vpopmail_sql does. It is configurable:
auth/auth_dbi DSN
(perldoc DBI for DSN) and you can also have:
auth_dbi_query
as a config file, which includes a custom SQL query (in case your
database has a different schema than mine). I'm just running out
the door now.
>
> I think we need a bit more infrastructure for tests - so that each
> plugin test can have its own config file. Perhaps even something that
> starts/stops qpsmtpd so we can test the server at the SMTP level as
> well as these unit tests.
>
> All a bit ambitious considering I'm pushing for a release. I'm
> wondering if we can push some of this issue to the next release?
Definitely. I just wanted to get the unit tests in ... not all the
other crap.
>
--
Guy Hulbert
[EMAIL PROTECTED] (preferred)
work: (416) 391-2051 (no voicemail)
cell: (416) 738-6257 (voicemail)
