in reply to Re: Re: Makefile.PL even weirder on Windows
in thread Makefile.PL even weirder on Windows

Moving the stuff to a t subdirectory, "nmake test" tells me that M1 etc. are not found. Apparently it does not chdir to the t directory before running the tests. How do I say in the Makefile.PL that the modules needed for the test scripts are also in that directory?

There isn't a way of doing this in the Makefile.PL that I am aware of. (Or, to be more accurate, no standard way. You can always write some custom code.)

People normally add the directory to @INC in the appropriate *.t files.

Also, what is the significance of the name 00-basic

Adding a number prefix is one way to define the order test scripts are run in.

Test are run in filename order. Some people like to have their test scripts run in a certain order. For example, you might test some basic stuff in the first script run and then bail out of the test suite if it fails - saving time when something goes wrong.

Replies are listed 'Best First'.
Re: Re: Re: Re: Makefile.PL even weirder on Windows
by John M. Dlugosz (Monsignor) on Jan 13, 2003 at 18:15 UTC
    I assume that the 1..m line applies to each file, not the whole set? The docs seem to imply the latter, but that makes things more difficult.

    Is the glob operator defined to return a list sorted by name? Ah yes, it's documented in File::Glob.

    —John

      I assume that the 1..m line applies to each file, not the whole set?

      Yup. It defines the number of expected tests for an individual test script.

      The docs seem to imply the latter, but that makes things more difficult.

      What does it make more difficult?

        What does it make more difficult?

        Because if that were the case, the 1..n line would have to be printed by the =first= file, which imposes that they be run in the proper order, and not easily run seperatly.