On Mon, 18 Sep 2006, Mauro Tortonesi wrote:
sorry, it's my fault. i was supposed to automate the testing process by writing a "glue" script which runs all the tests in sequence, but i never did it. i never got any feedback on the testing suite, so i thought nobody except me was using it, and i focused on other things.
np, understandable.
for the moment you're supposed to launch the tests in this way: perl -I. Test1.px
thanks! unfortunately, that doesn't work. neither does -I$PWD. i'm all for unit testing, which was why i started there first...but if the tests aren't ready for prime time, i don't mind skipping them. heaven:~/wget/tests> perl -I./ Test1.px Can't locate HTTPTest.pm in @INC (@INC contains: ./ /usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl/5.6.1 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0 .) at Test1.px line 5. BEGIN failed--compilation aborted at Test1.px line 5. heaven:~/wget/tests> same with -I$PWD. -Ryan -- http://snarfed.org/
