in reply to "make test" problems with previously installed module

That's a little odd because the tests are basically run as if they had been called like:

perl -Mblib t/test_file.t
which basically places the blib structure first in @INC. You might want to try running the tests by hand like the above in the first instance to see if that works as expected; it could be something in the test files themselves for instance rather than the module itself.

/J\

Replies are listed 'Best First'.
Re^2: "make test" problems with previously installed module
by geektron (Curate) on Sep 08, 2005 at 23:39 UTC
    i've tried:  perl -Mblib t/02_bad_constructor.t to no avail.

    i even tried adding a  use lib ("./t/testlib") in the .t script, but that didn't do it either.

    i am genuinely stumped.

      As long as you're mangling the test script anyway, I'd start with a dumping of @INC to see what's there, then a manual check of each directory in order to ensure that the module you think should be there is there. And the use lib line you've posted probably should warrant a check of the current working directory to ensure it's relative to where you think it should be. ;-)

        well, i added
        print "DIR: _$ \n" foreach @INC;
        and the results were pretty obvious ... the first directory is the site_perl directory that's throwing the errors (because the tests won't pass on the installed version ), and the second directory is the one added via command line.
Re^2: "make test" problems with previously installed module
by geektron (Curate) on Sep 08, 2005 at 19:09 UTC
    i find it odd myself, but i'll try this later when i can devote some time to this, and not dayjob work.