On 4/27/01 3:19 PM, "Chris Nandor" <[EMAIL PROTECTED]> wrote: > * Really, many of these tests should be run under MPW, and with ToolServer > available. That way paths will work properly, and the tests relying on > ToolServer (calling perl externally, calling "catenate", etc.) will work. > > * I realize that we need better instructions for people just downloading > the binary dist. I will work on that this weekend, or Monday/Tuesday. > Please feel free to hold off until then. I downloaded the binary dist last night and started running the tests (too lazy to build it right now). The major problem I had was with paths. So where, exactly should the 't' folder be relative to the lib folder when you're testing the binary dist? Right now I have it at the same level. I know that under Unix, most .t scripts are assumed to be run from one directory up, so relatively speaking, all of the test paths are one directory off if you're running under MacOS, right? (The 'fixes' in some of the test files for MacOS don't work at all when you're running them with the binary dist). Does running them under MPW fix that? Can you 'make test' under MPW and have it do the right thing? Or do we still have to run them one-by-one? (Probably a stupid question - if we could just 'make test' then all we'd have to do is send the nice little table the test harness spits out when it's finished...) Thanks, Todd -- Todd Richmond http://cellwall.stanford.edu/todd Carnegie Institution email: [EMAIL PROTECTED] Department of Plant Biology fax: 1-650-325-6857 260 Panama Street phone: 1-650-325-1521 x431 Stanford, CA 94305
