What do people think of the idea of amending the tests so they don't use CGI::Wiki::TestConfig at all, but simply use an SQLite database, skipping tests if DBD::SQLite isn't available? I've never been entirely happy with database access information hanging around, and the CGI::Wiki tests should catch any inconsistencies between databases - if they don't then they're incomplete.
I'm sort of fed up of having to faff with things when I'm running the OpenGuides tests, you see - if I'm just testing then I shouldn't have to answer questions.
Kake
On Wed 02 Jun 2004, Kate L Pugh kake@earth.li wrote:
What do people think of the idea of amending the tests so they don't use CGI::Wiki::TestConfig at all, but simply use an SQLite database, skipping tests if DBD::SQLite isn't available?
I'm going to implement this unless someone complains by the end of the day.
Kake
On Fri, 4 Jun 2004 14:30:45 +0100, Kate L Pugh wrote
On Wed 02 Jun 2004, Kate L Pugh kake@earth.li wrote:
What do people think of the idea of amending the tests so they don't use CGI::Wiki::TestConfig at all, but simply use an SQLite database, skipping tests if DBD::SQLite isn't available?
I'm going to implement this unless someone complains by the end of the day.
Actually I was thinking I approve. I just tried to upgrade OpenGuides where I've got two guides installed, and several various CGI::Wiki applications installed and well the tests didn't "just work" ... I ended up resorting to creating a fake guide that worked with a dummy database to test against.
-- Prather.org (powered by OpenWebmail, Perl, and Apache)
On Wed 02 Jun 2004, Kate L Pugh kake@earth.li wrote:
What do people think of the idea of amending the tests so they don't use CGI::Wiki::TestConfig at all, but simply use an SQLite database, skipping tests if DBD::SQLite isn't available?
OK, I've done this now. Can people grab the tarball from http://the.earth.li/~kake/code/OpenGuides-0.33_01.tar.gz and run the tests, please?
Kake
openguides-dev@lists.openguides.org
-
Chris -
Kate L Pugh