note Hanamaki ++ for tachyon's nice introduction to module installation. Since I have already done about 600-700 tests for the <A HREF="http://testers.cpan.org/">CPAN-testers</A> I would like to supply some comments (footnotes) from my experience. Some Footnotes 1. In our days, fortunately most authors use <code>h2xs</code> and <code>make dist</code>. Therefore, these tarballs expand to <code>Some-Module-0.01</code>, and if you <code>cd</code> into the directory you don't have to search for the place to do your <code>perl Makefile.PL</code>. Tarball distributions which expand just to <code>Some</code> are really a pain, especially if you download a few modules from the <code>Some::</code> Namespace. Unfortunately there are also some tarball distributions which don't get expanded in their own directories, but in the current directory -- Have fun with the cleanup afterwards. 2. Unfortunately, many CPAN authors are still not used to -- or don't know about -- setting <code>PREREQ_PM</code> in Makefile.PL. So be prepared to get the "Can't locate foo/bar.pm in @INC" error while running <code>make test</code>. 3. While you should find important information in the Readme File, don't be surprised if you just find a Readme template, where the author never cared to replace "blabla". 4. If <code>make test</code> just does one test (<code>1..1</code>) it is in most cases just a load test. This means, your module will get loaded without problems, but it does not tell you wether the supplied functions work as expected. While <code>make test</code> is a important step for confidence building you should test the Module with your own scripts, and report errors to the author if appropriate. Be prepared, that many tests supplied by the author do not test all functions. Hanamaki  Edited by [footpad], ~Wed Nov 28 20:04:16 2001 (GMT) 128077 128077